Ubuntu 22.04 LTS Nginx Fails Because Port 80 Is Already in Use

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

Nginx service fails to start, causing web applications to become unavailable.

Environment & Reproduction

Typical on Ubuntu 22.04 LTS when Apache or another process already binds port 80.

Root Cause Analysis

Only one process can bind the same IP:port unless special socket sharing is configured.

Quick Triage

Find current listener on 80 and decide whether to stop or reconfigure it.

Step-by-Step Diagnosis

Inspect nginx and competing service logs to confirm bind conflict source.

Solution – Primary Fix

Stop conflicting service or change nginx listen directive, then restart nginx.

Solution – Alternative Approaches

Keep both services by moving one to an alternate port and using reverse proxy routing.

Verification & Acceptance Criteria

nginx is active and HTTP responses return expected content on target endpoint.

Rollback Plan

Re-enable prior web service and restore original nginx server block if needed.

Prevention & Hardening

Document port ownership and enforce service startup order in deployment scripts.

Related Errors & Cross-Refs

Also appears with Docker published ports and stale orphaned listeners.

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

View all Ubuntu 22.04 LTS tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

See nginx troubleshooting docs and Ubuntu networking/service references.