• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Resolved intermittent 502 errors on sites

helpchrisplz

Basic Pleskian
Hi all.

So We keep getting random 502 errors on all our sites that we host using plesk 12.5
This happens multiple times throughout the day and normally lasts for about 10 - 15 mins at a time and then just starts working again.

Please can anyone advise me on what to do about it?
This is what i have done last time it went down:

ps -efww
and this is the output:
https://www.surgemarketingsolutions.co.uk/temp/ssh_output2.txt

I then tried this to make it come back online using the following but it didn't do much but it finally did come back after 6 mins or so:

[root@surge ~]# service nginx stop
[root@surge ~]# service httpd restart [ OK ]
Stopping httpd: [ OK ]
Starting httpd: [ OK ]
[root@surge ~]# apachectl graceful
[root@surge ~]# service nginx restart
Starting nginx: [ OK ]
[root@surge ~]# /etc/init.d/httpd status
httpd (pid 9159) is running...
[root@surge ~]# /etc/init.d/httpd restart
Stopping httpd: [ OK ]
Starting httpd: [ OK ]
[root@surge ~]#
 
ok probably found the problem:
Fail to ban was bannign apache
2016-12-12 14:11:16,058 fail2ban.actions [10960]: NOTICE [plesk-apache] Ban 88.208.205.107

Added 88.208.205.107 to the whitelist.


I expect that this has only become an issue recently now that we have a lot more sites so when there is an influx in the amount of traffic that apache needs to deal with then it must have been going over the failtoban limit.

Hopefully thats it.
 
Hi helpchrisplz,

pls. be informed, that you should ALWAYS whitelist "localhost" ( 127.0.0.1/8 ) and ALL your server - IPs, when you use Fail2Ban on your server - it has got nothing to do with a "Fail2Ban - limit", it is an essential setting. Pls. consider to read official documentations. ;)

 
Back
Top