Ubuntu 16.04 LTS Apache returns 503 because PHP-FPM socket missing

📖 ~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 HTTP 503 and application functionality is unavailable.

Environment & Reproduction

Appears after PHP package updates, service crashes, or misaligned socket path config.

Root Cause Analysis

Apache forwards requests to a PHP-FPM socket that is absent, inaccessible, or misnamed.

Quick Triage

Check PHP-FPM process state and verify expected socket file exists with correct permissions.

Step-by-Step Diagnosis

Compare Apache virtual host proxy target with php-fpm pool listen directive.

Solution – Primary Fix

Align socket paths, restart PHP-FPM and Apache, and clear stale runtime files.

Solution – Alternative Approaches

Switch to TCP upstream for PHP-FPM if socket permissions remain unstable.

Verification & Acceptance Criteria

Web requests return 200 and PHP pages render normally under load checks.

Rollback Plan

Revert virtual host and php-fpm pool configs to previous known-good versions.

Prevention & Hardening

Template service configs and validate post-update health checks automatically.

Related Errors & Cross-Refs

AH01079 failed to make connection, connect() to unix socket failed.

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

View all Ubuntu 16.04 LTS tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Apache + PHP-FPM integration guidance for Ubuntu 16.04 LTS stacks.