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

Issues with 503 error and Plesk domains

B

BrianDns

Guest
I have been having a reoccurring issue over the past few days with certain domains timing out on my server. I have around 60 or 70 domains and subdomains total on the Plesk server running CentOS 6.2 and Plesk 10.4.4. Usually I was noticing the issues on random subdomains only within one domain name. But I started seeing the issue pop up more frequently on regular domains now too. Usually when it happens it is only on anywhere from 1 - 10 domains only. Not all of them. It is also seemingly random. When it happens I restart apache and everything goes back to normal for a half hour up to a few hours then it all starts up again.

I didnt see anything in the logs that looks out of the ordinary. There is a bunch of stuff about SSL errors for the Plesk Panel Cert. I recently removed the SSL cert from the panel.

Does anybody have any ideas what could be happening. Please Help!!!!!!
 
Issue resolved

Thank you for the response abdi. You were definitely on the right track. I resolved the issue late last night.

The culprit was a fastCGI setting.

The setting was: fastcgimaxprocesses. It was set to 20. Everytime the 21st website would try to start up a process it would get denied by the server. Simple fix, but just brain racking when your in the situation.

Thank you again for getting back quick!
 
Back
Top