• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue All domains unreachable after upgrade to Plesk 17.8.11

Dukemaster

Regular Pleskian
Hi,
today I happily upgraded Onyx 17.5.3 #43 to 17.8.11 like suggested.
Upgrade was successful, but all domains/sites are unaccessible.
But it seems not a bug, much more related to configuration changes which belong to the upgrade, perhaps nginx.
Does anyone have a recommendation what to do, or what the reason might be?
Seems that others have the same problem. Don't want to destroy something by not necessary, stupid actions.

Greets
 
What do you mean by inaccessible sites? Does the browser return an error such as "connection refused" or do you see a default plesk page? Only with this information can I help you solve your problem.

As a matter of doubt, run the following command, it will check if all your Plesk settings are ok!

plesk repair all -n
 
^^^ yes like Emerson said ^^^

I actually have a daily crontab that runs a script that performs a "plesk repair all -n | strings" and emails me the output every morning just to make sure I'm informed right away when some auto-update decides to mess with me.
 
First step in this case is to check whether web servers are running
# service nginx status
# service httpd status
If not, try a restart
# service nginx restart
Then normally during the restart attempt an error message will be displayed why Nginx doesn't feel like going to work today ...
 
Hi there,

I'm experiencing a similar issue, during the upgrading operation to Plesk 17.8.11 it crashed. I managed to re-up Plesk by repairing the installation (plesk repair installation) but the db was inaccessible, so I ran a repairing routine (plesk repair db -y). After that Plesk restored and all the information of the hosted websites is now accessible (including databases), though the web server is returning the default page when trying to reach any of the hosted websites. Any idea?

BTW, I've already tried restarting Apache and Nginx.

Thanks!

Martin
 
So sorry folks, that I never replied what happened later in the early days of March.
I resolved the problem in the easiest way by switching to a new server.
Provider told me afterwards that it was it was finely the best decision. So I had to to do the Onyx upgrade once again.
This time successfully.
web server is returning the default page when trying to reach any of the hosted websites.
How to change default index file for a domain in Plesk
plus other possibilities:
HTTPs website loads Plesk default page instead of content
Domains show default page after Plesk upgrade and reconfiguration stucks
 
Last edited:
Back
Top