• 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 after today's System Updates

raykai

Basic Pleskian
all my websites are giving a 502 Bad Gateway after plesk did a auto System Updates...
i dont know where to start to find where the error is.

only thing i see in logs is:

1373#0: *41 connect() failed (111: Connection refused) while connecting to upstream nginx error

i did a full reboot and it did not help.
plz help
JlYWwOy.jpg
 
if i tern off Proxy mode (Nginx proxies requests to Apache Turn off to stop using Apache.) in Apache & nginx Settings then website works but then Nginx is not working.
this in on ‪Ubuntu 16.04.1 LTS‬
 
it seams that after the update my fail2ban banned my server IP under the jail: plesk-apache
this is the 1st time it dose this. any reson why it would bann its own IP for plesk-apache jail after a system update ?


deleting my servers IP from that jail fixed the error but im still wandering why it happen
 
You should always have your public IPv4 address and 127.0.0.1 added to the fail2ban whitelist to avoid such blocking.
 
Back
Top