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