Debian 11: Nginx cannot bind to port 80

📖 ~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 startup fails because another process already listens on port 80 or 443.

Environment & Reproduction

Service status shows bind address already in use and web traffic is unavailable.

Root Cause Analysis

Inspect listeners with `sudo ss -ltnp | grep -E ‘:80|:443’` and run `sudo nginx -t` for syntax checks.

Quick Triage

Competing web server, duplicate listen directives, or orphaned process from prior deployment.

Step-by-Step Diagnosis

Stop conflicting service or adjust listen ports and server blocks, then restart nginx cleanly.

Solution – Primary Fix

Confirm active listeners and successful health probe with `curl -I http://127.0.0.1`.

Solution – Alternative Approaches

Reserve port ownership per role and add pre-deploy checks for listener conflicts.

Verification & Acceptance Criteria

Reinstate previous nginx site configuration and service state from known-good release.

Rollback Plan

Include `nginx -t` and socket conflict tests in deployment pipelines.

Prevention & Hardening

`sudo ss -ltnp | grep -E ‘:80|:443’`; `sudo nginx -t`; `sudo systemctl restart nginx`

Related Errors & Cross-Refs

Provide listener table, enabled site files, and recent deployment diff for debugging.

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

Containerized reverse proxies on host networking can unexpectedly claim standard HTTP ports.