Thanks for the reply.
“You shouldn’t need to assign the public IP to a VirtualHost the private one is fine. In the AWS Console map the Elastic Public IP to the running instance and you can then access the Virtualmin server from the public IP.”
I can successfully access VirtualMin on the Public IP; this worked fine out of the box.
However the Public IP still is not landing on my newly created VirtualHost - it is still taking me to the default /var/www/html
I have done this:
“Server Configuration > Change IP Address you should see that the ‘Current IP’, ‘Shared Address’ and ‘Real Address’ all reflect the private IP. The External Address will have the optional input field showing your Elastic Public IP.”
I’ve taken some screenshots, please see below.
I’ve blanked out some parts of the two IPs but to help explain:
Private IP = 172.xx.xx.172
Public IP: 52.xx.xx.111
And my virtualhost created is set to sit at /home/virtualhostname/
However, going to the public IP 52.xx.xx.111, I am being sent to the default, which is /var/www/html
Perhaps it’s a different issue, as on the public IP on port 80 I DO successfully see the default ubuntu landing page, BUT it’s at /var/www/html, and NOT the one VirtualHost I have set up, which is at /home/virtualhostname/public_html – so somewhere I’m not telling that VirtualHost to be on my public IP. Perhaps as illustrated by the screenshot " View / Edit Virtual Server Info" below, even though the “External IP Address” for this VHost is set to the public one.
Am I missing a step somewhere?
Virtualmin > System Settings > Virtualmin Configuration > Network Settings
Default IP address for DNS = Other ==> Public IP
IP Address setting of my VirtualHost:
External IP = Public IP
All other IPs here = Private IP
View / Edit Virtual Server Info:
IP Address is shown as the Private one