• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Resolved Plesk 12.5: 502 bad gateway

FYI - I confirm I have ModSec enabled with basic rules. So potentially 12.5.30 Update 4 might solve the apache restarts. I'll let you know.
 
Check entries in /etc/sw-cp-server/config - http-Block:

http {
fastcgi_buffers 32 32k;
fastcgi_buffer_size 64k;
fastcgi_read_timeout 600;
fastcgi_send_timeout 600;
}

if not like this - Edit and save.
Before i had 16 16k and buffer size 32k
After that change, never had problems again.
 
Hello

Same happened to me getting 502 error gateway nginx. Doing some investigating led me to plesk fail2ban! There I noticed my control panel ip was banned thus affecting all vhosts. Unbanning my control panel ip made everything work again when I started nginx. But why was my ip banned well looking into when this happened, it was the time we where installing ssl certificate. Just for your info.

Cheers! Any comments are appreciated.
 
Unbanning my control panel ip made everything work again

The VERY FIRST thing to do, BEFORE you switch on Fail2Ban on your server, is to whitelist ALL server IPs and localhost, to avoid issues as described. ;)

Pls. see: => /etc/fail2ban/jail.conf
...
...
[DEFAULT]

# "ignoreip" can be an IP address, a CIDR mask or a DNS host. Fail2ban will not
# ban a host which matches an address in this list. Several addresses can be
# defined using space separator.
ignoreip = 127.0.0.1/8 XXX.XXX.XXX.XX1 XXX.XXX.XXX.XXX2 XXX.XXX.XXX.XXX3
...
 
Back
Top