I already took a peak… it was showing the correct websites before i deleted both vhosts and recreated them. This is a fresh install of virtualmin. All I’ve done is create gatesofanrah.com delete it, and then recreate it.
Under network settings I set it to use 67.216.104.94 as the default virtual server ip instead of 192.168.1.10, and I set it up to use full name under defaults for new domains ie ‘gatesofanrah.com’ for user creation instead of partial ie ‘gatesofanrah’.
I have not modified the apache config manually.
Virtualmin Module Configuration under the Other Server Settings category, I could not find this…
if zapphost is the first domain in the sites-enabled than it would make sense that it would show up. Apache just looks at the first site it encounters and that is usually the first site listed.
recreating the gatesofanrah probably made it second in the list.
ah i misunderstood, i though you tried to reach the server by IP.
Why is zapphost on a LAN IP < VirtualHost 192.168.1.10:80> in the config and gatesofanrah not?
No, my server was displaying zapphost.com correctly, and gatesofanrah.com correctly by just pointing the domain to my servers ip. This SHOULD be working, it should be using the domain to decide what page is served…
apache thoughts… “hey they are asking for gatesofanrah.com on 67.216.104.94, let’s display /home/gatesofanrah.com/public_html/DIRECTORY INDEX”
apache thoughts… “hey they are asking for zapphost.com on 67.216.104.94, let’s display
/home/zapphost.com/public_html/DIRECTORY INDEX”
Does virtualmin not install mod_vhost_alias? If I remember correctly this is what allows apache to think like this. If not or there are no alternatives, I’m going to be switching control panels, cause that is rather stupid that clients HAVE to use my nameservers.
zapphost.com is the fully qualified domain name for the server.
I noticed zapphost.com.conf is still using the old settings 192.168.1.10 as the vhost directive.
gatesofanrah.com.conf is using the new setting i input 67.216.104.94
it is on that because when virtualmin was configured, it used my lan ip for the default… it warned me i should set it to wan and I did… would setting that to wan ip maybe fix my probs?
apache listens to 1 address. having 2 sites on two different IP’s is asking for problems (its not totally true as I use 3 IP’s for different sites but then it needs to be configured for that).
if you are not behind NAT then you should use the reachable IP which is 67.216.104.94 for apache
Ok I set it to use 67.216.104.94 on zapphost.com.conf and i rebooted, it will take ~3 mins for my server to reboot it has to rebuild something for raid 1 everytime >.>
yea, i always have problems restarting apache, it acts like apache is already running and it never shutdown and it starts a bunch of apache processes and i have to killall… its a big mess… rebooting is easier…
Now all I’m getting is “It Works”. From both domains after i set zapphost.com.conf vhost to use 67.216.104.94 >.>
per haps your server is working as a router too?
You need to check out the networking config and related modules. In principle there shouldn’t be a mention of a LAN IP if you are directly contected to the web.
The permission denied is probably a deny all in the apache config and may go away when a index is placed.
is this a dedicated server that you first configured at home?
I didn’t see a Listen directive in your config so Apache will listen to anything probably which is worse.
this is a server at my house, it is behind a router and i’ve port forwarded all need ports to this machine… i have an index.php in the public_html directory of gatesofanrah.com
I added this to get phpmyadmin working on all sites, let me fix it… i can tell i did some things wrong…
Ah I thought it was at a datacenter since you configured the WAN address.
In that case, yes Apache needs to listen to your LAN IP and both domains must be configured to 192.168.1.10
Then under virtualmin go to system settings-module config-network settings and set Default virtual server IP address to 192.168.1.10
set Default IP address for DNS records to 67.216.104.94
the permission denied may have to do with apache not knowing where to go in your current configuration.
I was retarded… deleted the files in the directory and forgot about it… i uploaded the files now everything is working great… thank you for your help ronald! I’m sure I’ll have more questions in the future.