Skip to content

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

Website shows 502 Bad Gateway? nginx, PHP-FPM crashed, Plesk error, disk full – webspace troubleshooting step by step.

Webspace

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.

Related

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.
Next Fix SSL Errors – Activate HTTPS Immediately (Let's Encrypt)

Keep reading

Popular and fresh – not just the oldest guides.

Webspace Fix SSL Errors – Activate HTTPS Immediately (Let's Encrypt) Set up SSL/HTTPS correctly – certificates, HSTS and secure configuration with NexoraHost. Webspace Webspace – All Information Webspace – All Information – Web hosting and domain knowledge from NexoraHost. Webspace pache vs. Nginx – Which Web Server Suits You? pache vs. Nginx – Which Web Server Suits You? – Web hosting and domain knowledge from Nexo... Webspace Emails Landing in Spam – SPF, DKIM, DMARC & Sender Reputation Emails from your domain land in spam folder? SPF, DKIM, DMARC, reverse DNS & sender addres... Webspace Web Technologies Web Technologies – Web hosting and domain knowledge from NexoraHost. Webspace Fix PHP Errors – Fatal Error, Memory Exhausted & Plesk PHP fatal error or "Allowed memory size exhausted"? Plesk error.log, memory_limit, faulty...
More

Explore NexoraHost