Resolved All site shows plesk default page after upgrading from 10.4.4 to 11.0.9

[Freshlinx]

Thank you! I too had the same problem after an upgrade, two subscriptions missing from plesk, server health red CPU warnings and all sites redirecting to the Apache Test Page. Your reconfigure command did the trick (for now!)... Still have two subscriptions missing and so I am unable to access the control panels for these domains...

 

[johnrt]

This is getting me too. I have an AWS installation of Plesk on CentOS 6.3. Plesk v11.5.30. Both my main domain (www) and a subdomain can be "preview" fine, but "open" from "websites & domains" (or directly from a browser) go to the default Plesk pages. I have resaved "hosting settings", restarted the server, and tried "httpdmg --reconfigure-all" and the same thing is occurring. Not certain what else can be tried

 

[gholsie]

Hi all, I ran into this problem today after doing a service pack upgrade. The only way I was able to get around it was to go into every domain setting. I suspended each domain and then re-enabled each one separately. After doing this, the sites came back online. I only have less than 10 sites, so, I could imagine how this would affect large sites with thousands of domains. Sorry guys, but the developers at Parallels just don't seem to think about things like this. Too bad, but I do still like Plesk for the other features. I'll just be prepared to do extra work after every upgrade.

Mike

 

[SPEAKnSPAN]

Same problem. After reboot, Nginx doesn't work and I have this message in the LOGS

2014/06/25 12:42:48 [emerg] 2995#0: bind() to [2001:41d0:2:1de3::]:80 failed (99: Cannot assign requested address).

and Server health red CPU warnings

I need to restart Nginx by terminal command :

# service nginx restart

I tried this solution but doesn't work : http://kb.parallels.com/en/114245

MY CONFIG : Linux Plesk 11.5 (CentOS 6) (64bits)

Thanks for your help

D.

 

[jonathan7799]

Hi,

I know this is an old thread, but I just did an upgrade from Plesk 12 to 17 and I found that all my sub domains defaulted to the standard webs server default page.

I realised after much messing around that the index.html file had appeared in the root directory of the sub domains and was causing the problem.

Simply deleting the html file got rid of the page

J.

 

[KDawson]

FYI, I also ran across the "all sites go to default" problem after I created a new Digital Ocean droplet from a backup. All the httpd.conf files in /var/www/vhosts/system/*/conf had statements <VirtualHost xxx.xxx.xxx.xxx:80 > and <... :443 > with the original IP address. I could edit these one by one or en mass to specify the new IP address; or regenerating them should use the new IP.