• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

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