• 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.

Resolved Customers can't access plesk panel after update

seqoi

Regular Pleskian
Yesterday i updated to Plesk 17.5.3 Update #4 and all other packages are definitely updated to latest version. Server restarted.

After that update (17.5.3 Update#4) every customer on every domain under subscription can't access their Plesk panels anymore.

It worked great and smooth up until i updated yesterday. Everything else work, Apache, websites, email everything works. I can log in as admin in plesk and i can access customer Plesk account through "Log in as customer".

It's just that they can not access it anymore when they type in

http://www.somedomain.com:8443/ - Plesk panel not working for them anymore and they get:

400 Bad Request
The plain HTTP request was sent to HTTPS port
nginx

Any clue? Advice? Which log file should i look into? Oh boy it worked wonderfully until yesterday i hope update won't cause more issues...
 
Back
Top