Fix 502 Bad Gateway – nginx, PHP-FPM & Plesk

Quick answer: 502 Bad Gateway: restart PHP-FPM, check disk space, disable faulty plugin and increase PHP memory_limit.

If you landed here: Browser shows "502 Bad Gateway" instead of your website.

Frequently asked questions (FAQ)

502 Bad Gateway – what does it mean?

Web server (nginx) can't reach backend (PHP-FPM). PHP process crashed, overloaded or disk full.

502 after plugin update (WordPress)?

Disable plugin via FTP (rename folder in wp-content/plugins). Increase PHP memory limit.

502 only sometimes?

PHP-FPM max_children too low or RAM limit hit. Plesk → PHP settings → increase memory_limit.

NexoraHost

SSD hosting with free SSL, email mailboxes & Plesk panel.

Order now → Account

nexorahost.com · Maincubes FRA01 · 1 Tbit/s DDoS · 99,9 % Uptime