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

Issue EOL 12.5 on 01/01/19 - getting 503 errors.

viziony

New Pleskian
Starting on 1/1/19 @ 5:35 AM EDT, my website started to experience ngnix 503 communication errors. I tried restarting the Plesk service which does not help, I would have to manually REBOOT my linux server in order to restored connectivity. Connection on port 8880 basically is hung unless I restart. Is this related to the EOL on Plesk 12.5 and I need to go onto Plesk Onyx?

Can I just use the GUI Plesk Installer to perform this upgrade and also would this fix my 503 errors? I am having to reboot the server at least twice a day now since 01/01/19.

Receiving a lot of these within the logs when the connection issue happens :

939#0: *172418 upstream timed out (110: Connection timed out) while reading response header from upstream
 
Back
Top