• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.

New Websites/Domains only load default page?

Status
Not open for further replies.

yabado

Regular Pleskian
I did some searching before posting, but could not find a definitive answer.

I am creating new sites in my panel and they are only loading the default page.

The IP is pointed correctly or I would not get the default plesk page.

All the other service seem to work ok. I can ftp in and I can edit files with the online file manager.

If I use the preview feature I can see the changes I make to the files, but that is the only way.

I looked in /var/www/vhosts/system/ and the conf files are present.

What else can I check to see why the sites are not working?
 
You will have to rebuild httpd config file on your server with the following command

Code:
/usr/local/psa/admin/sbin/httpdmng --reconfigure-all
 
You will have to rebuild httpd config file on your server with the following command

Code:
/usr/local/psa/admin/sbin/httpdmng --reconfigure-all

Is this something I will need to do every time I ( or customer ) add a new domain/site?
 
I have once had this situation when I had DNS-records for the domain in ipv4 and ipv6 but forgot to configure ipv6 for the website in Plesk.
 
OK, I discovered the issue and I am embarrassed I missed it.

My PP is running on a AWS EC2 VPC instance. Which means, I need to use the VPC internal IP address for my virtual hosts AND NOT the elastic IP facing the public.

For example using the following setup...

(public EIP) 123.456.78.90 points to (internal VPC IP) 10.0.0.199

I would need to assign the 10.0.0.199 IP to my domains/websites.

Hopefully this will help someone else down the road.

case closed.
 
Status
Not open for further replies.
Back
Top