• 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!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    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.

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