• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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