HELP /var/www/public.html "It Worked" page served for all domains?
-
pistolgrip
- Posts: 5
- Joined: Sat Aug 20, 2016 12:58 pm
HELP /var/www/public.html "It Worked" page served for all domains?
I've been struggling trying to get VestaCP setup and configured properly for a few days now. After much research, problem solving, and issue fixing I finally thought everything was working correctly. All DNS, Email, and DB servers/features seem to be working as desired. Finally.
It took me a bit to figure out it was happening. But, all domains added in Vesta are being served /var/www/public.html instead of the /home/admin/<domain>/public.html file as expected.
I've tried changing different templates including basedir, default, and hosting and nothing seems to make any difference. I've looked through the logs and .conf files, and everything appears correct as far as I can tell.
I've tried all the fixes and read all the posts I could find here and elsewhere, but cannot figure it out. If anyone has any ideas, or needs more information to help, please let me know. I'm about to pull my hair out.
Thanks.
It took me a bit to figure out it was happening. But, all domains added in Vesta are being served /var/www/public.html instead of the /home/admin/<domain>/public.html file as expected.
I've tried changing different templates including basedir, default, and hosting and nothing seems to make any difference. I've looked through the logs and .conf files, and everything appears correct as far as I can tell.
I've tried all the fixes and read all the posts I could find here and elsewhere, but cannot figure it out. If anyone has any ideas, or needs more information to help, please let me know. I'm about to pull my hair out.
Thanks.
-
pistolgrip
- Posts: 5
- Joined: Sat Aug 20, 2016 12:58 pm
Re: HELP /var/www/public.html "It Worked" page served for all domains?
SUCCESS.
Thought I would post a follow-up on how I solved the issue. Turns out it was related to me adding and binding the VM's public IP (This is an Azure Ubuntu 14.04 VM).
I removed the public IP from the server on eth0, removed the <publicIP>.conf files from ngix and apache configs and rebooted. Then, I deleted the Public IP entry from the VestaCP IP list, and added the public IP in the NAT field of the internal IP in the list.
After rebooting and restarting Vesta everything seems to be working. Now we can move on to actually getting some sites up and running.
Thanks to XoXiLhJ0mn who's insight shared @ viewtopic.php?f=11&t=12376 gave me another thing to try and ultimately helped find the solution.
Thought I would post a follow-up on how I solved the issue. Turns out it was related to me adding and binding the VM's public IP (This is an Azure Ubuntu 14.04 VM).
I removed the public IP from the server on eth0, removed the <publicIP>.conf files from ngix and apache configs and rebooted. Then, I deleted the Public IP entry from the VestaCP IP list, and added the public IP in the NAT field of the internal IP in the list.
After rebooting and restarting Vesta everything seems to be working. Now we can move on to actually getting some sites up and running.
Thanks to XoXiLhJ0mn who's insight shared @ viewtopic.php?f=11&t=12376 gave me another thing to try and ultimately helped find the solution.