Debian 10 – Nginx returns 502 because PHP-FPM is unavailable – Fix & Prevention

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution – Primary Fix
7. Solution – Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

Dynamic pages fail with 502 responses while static files still load.

Environment & Reproduction

Seen after PHP upgrades, socket path changes, or FPM pool misconfiguration.

Root Cause Analysis

Nginx upstream cannot reach active PHP-FPM socket or process listener.

Quick Triage

Check PHP-FPM service state and compare socket path in both configs.

Step-by-Step Diagnosis

Inspect error logs, permissions, and process limits for pool exhaustion.

Solution – Primary Fix

Align upstream settings, restart services, and validate pool health.

Solution – Alternative Approaches

Switch from unix socket to TCP upstream if socket permission issues persist.

Verification & Acceptance Criteria

PHP endpoints return successful responses under representative load.

Rollback Plan

Restore prior Nginx/FPM configurations and package versions if needed.

Prevention & Hardening

Pin compatible package sets and include post-upgrade smoke tests.

Related Errors & Cross-Refs

Often associated with FPM crash loops and exhausted worker limits.

Related tutorial: View the step-by-step tutorial for Debian 10.

View all Debian 10 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Nginx and PHP-FPM integration best practices on Debian.