• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

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