Hello,

127.0.0.1 is only configured for site2 -- is it a bug or a feature? Are you testing it from the same host, or via proxy on the same host?
--

With Best Regards,
Marat Khalili

On September 28, 2015 10:06:04 PM GMT+03:00, Felix Rubio <chronos@kngnt.org> wrote:

Hi everybody :-)

 

I have an Apache server (2.4) running on a Debian testing. Because I need to access some sites from Internet (iface 192.168.1.2)(with and without SSL), some others through a VPN (iface 10.8.0.1) and some others are purely local to the server (iface 127.0.0.2), I have created the following setup:

ports.conf:

Listen *:80

Listen *:443

site external and internal (same .conf):

<VirtualHost 192.168.1.2:443> --> SSL-enabled

ServerName site0.example.org

....

</VirtualHost>

<VirtualHost 10.8.0.1:80> --> Not SSL-enabled

ServerName site0.example.org

....

</VirtualHost>

site only internal (same .conf):

<VirtualHost 10.8.0.1:80> --> Not SSL-enabled

ServerName site1.example.org

....

</VirtualHost>

site internal, external, and local (same .conf):

<VirtualHost 10.8.0.1:80 127.0.0.1:80> --> Not SSL-enabled

ServerName site2.example.org

....

</VirtualHost>

<VirtualHost 10.8.0.1:443 192.168.1.2:443> --> SSL-enabled

ServerName site2.example.org

....

</VirtualHost>

The problem is: when I try to access the with any browser site1, I get in the address bar of the browser the URL from site0, and what is loaded is site2 (¿¿??). I have been searching for a solution for some days but I can not find my way through. Am I doing something dramatically wrong? Any help will be appreciated. Thanks!

Felix