Join Log in
Score:0
Loki avatar Server

Azure VM and Multiple Apache Instances

td flag
Loki

I am doing some experiments and trying to setup multiple websites on 1 host without it being obvious that the websites are related. I want them to have their own IP address and names.

I have added an IP Alias to the interface in the Azure console, so the VM has two Public IPs linked to two Private IPs, for example:

172.1.1.1 -> 21.1.1.1
172.1.1.2 -> 21.1.1.2

I have followed the apache guide to setup two httpd instances, but I am having issues modifying the Listen directive in ports.conf to get them to listen on different IPs.

Listen 80

<IfModule ssl_module>
    Listen 443
</IfModule>

<IfModule mod_gnutls.c>
    Listen 443
</IfModule>

Azure seems to do some NAT so the VM isn't aware of its Public IPs, so I assume I have to use their Private IPs. If I modify the file to:

Listen 172.1.1.1:80

<IfModule ssl_module>
    Listen 172.1.1.1:443
</IfModule>

<IfModule mod_gnutls.c>
    Listen 172.1.1.1:443
</IfModule>

Then the website just becomes unreachable and there is nothing obvious in the error logs. Any suggestions?

The same thing happens if I use the Public IP:

Listen 21.1.1.1:80

<IfModule ssl_module>
    Listen 21.1.1.1:443
</IfModule>

<IfModule mod_gnutls.c>
    Listen 21.1.1.1:443
</IfModule>
19
0 + 0
ธงชาติไทย
Elon Musk
I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.