Debian 11: Apache returns 503 because PHP-FPM socket is 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 503 because Apache cannot reach the configured PHP-FPM backend socket.

Environment & Reproduction

Static assets load but PHP endpoints return 503 and proxy_fcgi errors in logs.

Root Cause Analysis

Check `systemctl status php7.4-fpm`, verify socket files in `/run/php/`, and inspect Apache error logs.

Quick Triage

FPM service stopped, socket path mismatch, or permissions prevent Apache from connecting.

Step-by-Step Diagnosis

Align Apache proxy target with active FPM socket, ensure service runs, and reload both daemons.

Solution – Primary Fix

Request a PHP health page and confirm no new backend connection errors in Apache logs.

Solution – Alternative Approaches

Pin PHP package versions and template socket paths from a single source of truth.

Verification & Acceptance Criteria

Revert virtual host and FPM pool files to prior working revision and reload services.

Rollback Plan

Run continuous health checks that validate both HTTP response and PHP execution path.

Prevention & Hardening

`systemctl status php7.4-fpm`; `ls -l /run/php`; `sudo apachectl configtest`

Related Errors & Cross-Refs

Share Apache vhost snippets, FPM pool config, and permission model for socket directory.

Related tutorial: View the step-by-step tutorial for debian-11.

View all debian-11 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Upgrading PHP minor versions can change socket names and break hardcoded proxy targets.