• 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 502 bad gateway error on all domains

@Pascal_Netenvie

I am pretty sure that Fail2Ban is not the root cause of the problem, at least not on a default Plesk + Fail2Ban instance.

Any customization of Fail2Ban (custom actions, custom log scanning etc.) can cause this "odd" behaviour by Fail2Ban, but it is fairly rare (and it can be prevented).

Anyway, I certainly hope that you are not seeing the error notifications anymore.

Regards
 
Hi Guys
I found why i had this error regularly ... it is simple and pretty stupid ! o_O

Fail2ban just autoban the server and add its own IP adress to blacklist ...
So just check if your server IP address is in Fail2ban blacklist and add it to whitelist !

Then you can restart NGINX and enjoy fullspeed.

Ref post : https://talk.plesk.com/threads/12-5-30mu4-nginx-stopped-possibly-after-installing-wordpress.334826/

Cheers.:)

how is that possible? just with 2 wp and 1 piwik its been running for 12 day now
 
I am pretty sure that Fail2Ban is not the root cause of the problem, at least not on a default Plesk + Fail2Ban instance.

Yeah in my case 2 things to note :
1 - I made agressive setup in fail2ban cause this new server host 2 sites that have been hacked 2 weeks before on other host that was not ours and not secured.
2 - The server IP was ban after someone try to attack so there was kind of Dos or bruteforce, so NGINX send lot of request to Apache and server IP falled in Modsecurity Jail !

Logic !
 
Same issue, but this time on plesk onyx

You mean, you made the VERY SAME mistake again, to forget to add your localhost and the IPs on your server as "Trusted IP Adresses"??? Kingsley, you really should start to INSPECT your log - files ( Fail2Ban - log AND the domain - specific webserver - log - files and the used jails, because Fail2Ban doesn't ban unintentionally, there is a reason, why your IPs are being banned!
 
You mean, you made the VERY SAME mistake again, to forget to add your localhost and the IPs on your server as "Trusted IP Adresses"??? Kingsley, you really should start to INSPECT your log - files ( Fail2Ban - log AND the domain - specific webserver - log - files and the used jails, because Fail2Ban doesn't ban unintentionally, there is a reason, why your IPs are being banned!

@UFHH01 my IP was added same as local hostIP Address Banning   Kraftysprouts Hosting.jpeg
 
You mean, you made the VERY SAME mistake again, to forget to add your localhost and the IPs on your server as "Trusted IP Adresses"??? Kingsley, you really should start to INSPECT your log - files ( Fail2Ban - log AND the domain - specific webserver - log - files and the used jails, because Fail2Ban doesn't ban unintentionally, there is a reason, why your IPs are being banned!

Code:
2016/10/22 20:00:03 [error] 5253#0: *55050 connect() failed (111: Connection refused) while connecting to upstream, client: 23.96.184.72, server: kraftysprouts.com, request: "GET / HTTP/1.1", upstream: "https://45.33.123.217:7081/", host: "www.kraftysprouts.com"
2016/10/22 20:01:03 [error] 5253#0: *55064 connect() failed (111: Connection refused) while connecting to upstream, client: 23.96.184.72, server: kraftysprouts.com, request: "GET / HTTP/1.1", upstream: "https://45.33.123.217:7081/", host: "www.kraftysprouts.com"
2016/10/22 20:02:03 [error] 5253#0: *55072 connect() failed (111: Connection refused) while connecting to upstream, client: 23.96.184.72, server: kraftysprouts.com, request: "GET / HTTP/1.1", upstream: "https://45.33.123.217:7081/", host: "www.kraftysprouts.com"
2016/10/22 20:03:03 [error] 5253#0: *55088 connect() failed (111: Connection refused) while connecting to upstream, client: 23.96.184.72, server: kraftysprouts.com, request: "GET / HTTP/1.1", upstream: "https://45.33.123.217:7081/", host: "www.kraftysprouts.com"
2016/10/22 20:04:03 [error] 5253#0: *55098 connect() failed (111: Connection refused) while connecting to upstream, client: 23.96.184.72, server: kraftysprouts.com, request: "GET / HTTP/1.1", upstream: "https://45.33.123.217:7081/", host: "www.kraftysprouts.com"
2016/10/22 20:05:03 [error] 5253#0: *55114 connect() failed (111: Connection refused) while connecting to upstream, client: 23.96.184.72, server: kraftysprouts.com, request: "GET / HTTP/1.1", upstream: "https://45.33.123.217:7081/", host: "www.kraftysprouts.com"
2016/10/22 20:06:03 [error] 5253#0: *55124 connect() failed (111: Connection refused) while connecting to upstream, client: 23.96.184.72, server: kraftysprouts.com, request: "GET / HTTP/1.1", upstream: "https://45.33.123.217:7081/", host: "www.kraftysprouts.com"
2016/10/22 20:07:02 [error] 5253#0: *55136 connect() failed (111: Connection refused) while connecting to upstream, client: 23.96.184.72, server: kraftysprouts.com, request: "GET / HTTP/1.1", upstream: "https://45.33.123.217:7081/", host: "www.kraftysprouts.com"
2016/10/22 20:08:03 [error] 5253#0: *55155 connect() failed (111: Connection refused) while connecting to upstream, client: 23.96.184.72, server: kraftysprouts.com, request: "GET / HTTP/1.1", upstream: "https://45.33.123.217:7081/", host: "www.kraftysprouts.com"
2016/10/22 20:09:03 [error] 5253#0: *55179 connect() failed (111: Connection refused) while connecting to upstream, client: 23.96.184.72, server: kraftysprouts.com, request: "GET / HTTP/1.1", upstream: "https://45.33.123.217:7081/", host: "www.kraftysprouts.com"
2016/10/22 20:10:03 [error] 5253#0: *55195 connect() failed (111: Connection refused) while connecting to upstream, client: 23.96.184.72, server: kraftysprouts.com, request: "GET / HTTP/1.1", upstream: "https://45.33.123.217:7081/", host: "www.kraftysprouts.com"
2016/10/22 20:11:02 [error] 5253#0: *55211 connect() failed (111: Connection refused) while connecting to upstream, client: 23.96.184.72, server: kraftysprouts.com, request: "GET / HTTP/1.1", upstream: "https://45.33.123.217:7081/", host: "www.kraftysprouts.com"
2016/10/22 20:12:03 [error] 5253#0: *55235 connect() failed (111: Connection refused) while connecting to upstream, client: 23.96.184.72, server: kraftysprouts.com, request: "GET / HTTP/1.1", upstream: "https://45.33.123.217:7081/", host: "www.kraftysprouts.com"
2016/10/22 20:13:03 [error] 5253#0: *55249 connect() failed (111: Connection refused) while connecting to upstream, client: 23.96.184.72, server: kraftysprouts.com, request: "GET / HTTP/1.1", upstream: "https://45.33.123.217:7081/", host: "www.kraftysprouts.com"
 
Back
Top