Ubuntu 18.04 LTS Nginx returns 502 Bad Gateway to upstream

📖 ~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

Clients receive 502 errors, causing partial application outage.

Environment & Reproduction

Nginx reverse proxy in front of app server over Unix/TCP socket.

Root Cause Analysis

Upstream process down, misrouted socket path, or timeout mismatch.

Quick Triage

Validate backend process health and immediate Nginx error log context.

Step-by-Step Diagnosis

Trace proxy_pass endpoint, socket permissions, and timeout settings.

Solution – Primary Fix

Restore upstream service and align proxy timeout/buffer configuration.

Solution – Alternative Approaches

Add backup upstreams and health checks for graceful failover.

Verification & Acceptance Criteria

Sustained 200 responses and no upstream errors in logs.

Rollback Plan

Revert to previous Nginx site config and reload safely.

Prevention & Hardening

Implement synthetic checks and supervised backend restarts.

Related Errors & Cross-Refs

Differentiate 504 timeout cases from immediate 502 upstream failures.

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

View all Ubuntu 18.04 LTS tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Nginx upstream documentation and Ubuntu web stack troubleshooting.