Ubuntu 14.04 LTS – Apache returns 502 due to PHP-FPM backend issues – 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

Users receive 502 responses and dynamic pages fail to render.

Environment & Reproduction

Appears after PHP-FPM restarts, socket path changes, or worker exhaustion.

Root Cause Analysis

Apache cannot reach healthy PHP backend due to socket or process issues.

Quick Triage

Check Apache and PHP-FPM status, then inspect upstream errors.

Step-by-Step Diagnosis

Review vhost proxy directives, socket permissions, and pool utilization.

Solution – Primary Fix

Correct socket/port mapping, restart services in order, and tune pools.

Solution – Alternative Approaches

Switch to TCP backend path if socket permission complexity persists.

Verification & Acceptance Criteria

HTTP 200 responses resume and backend error rates drop to normal.

Rollback Plan

Restore previous Apache and PHP-FPM config set if regression appears.

Prevention & Hardening

Add health checks and capacity limits for PHP worker pools.

Related Errors & Cross-Refs

Related to upstream timeout, max children reached, and socket missing events.

Related tutorial: View the step-by-step tutorial for Ubuntu 14.04 LTS.

View all Ubuntu 14.04 LTS tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Apache reverse proxy and PHP-FPM tuning guidance.