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

Wordpress Site causing 504 Bad Gateway on 11.5.30

J

JWT-Tech

New Pleskian
I am hosting about 10 WordPress sites on 11.5.30 Update #20 CentOS 5.10. I recently upgraded from Plesk 11.0 and have been having an issue with one of the WordPress sites. It randomly causes nginx to give a bad gateway 504 error that never goes away unless I reboot the server, the apache service or run httpdmng --reconfigure-all. Any of those fix the issue but after a few hours or days its back and the customer is telling me the site has been down for a few hours. I am trying to figure out if this is an issue with my server or an issue with this WordPress install that is causing the issue. Anyone got any ideas?
 
Last edited:
You must log in or register to reply here.

Similar threads

C
Issue Gateway timeout
Replies
3
Views
759
Bitpalast
Bitpalast
R
Resolved WP Toolkit/Wordpress Toolkit - older version screenshot issue
Replies
4
Views
3K
rhall
R
D
Issue 502 Bad Gateway - New Install - Restored from Backup
Replies
10
Views
2K
MartinT
M
B
Issue High latency, unreliable performance & 522 errors on a Plesk server that ran fine for 6+ months
Replies
8
Views
2K
HHawk
HHawk
E
Issue Abnormal CPU usage and Apache crash
Replies
13
Views
4K
MartinT
M
Back
Top