• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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