• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

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