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

Plesk 11 Error 503 on Ubuntu 12.04

webhod

New Pleskian
Hi all,

from time to time I´m getting a 503 error message (Service not available) when accessing the panel site (https://hostname:8443). All other hosted homepages are working without any issues. It seems that just the panel crashes. I couldn´t find anything in the logs (/usr/local/psa/admin/logs/panel.log, /var/log/sw-cp-server/error_log) related to this. Nginx and Apache logs are clean as well...

I noticed that message when I´m accessing the Panel login site and Plesk redirects to "relay" (https://hostname:8443/relay => then to https://hostname:8443/sso/ui). It stops on the "relay" page with mentioned error message. Maybe this will help you to find the error.

When I restarted Plesk using /etc/init.d/psa restart anything works fine... Until the next crash in a few days...

I already read the kb regarding to this issue on windows servers but I could not find anything for linux systems...

OS is Ubuntu 12.04, Plesk runs on a dedicated server, not inside a VZ Container.

Any ideas?
Thanks in advance!

Chris
 
Back
Top