Ubuntu 20.04 LTS – Common Problem 011 – Diagnosis and Fix

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

Service is running locally but unreachable remotely, causing application outage perceptions.

Environment & Reproduction

Ubuntu 20.04 with ufw enabled and default deny inbound policy.

Root Cause Analysis

Required port/protocol not explicitly allowed, interface-specific rules missing, or rule order confusion.

Quick Triage

Check ‘sudo ufw status numbered’, service bind address, and external path with nc/curl tests.

Step-by-Step Diagnosis

Map listening sockets to expected firewall rules and confirm no upstream ACL/cloud SG mismatch.

Solution – Primary Fix

Add precise allow rule such as ‘sudo ufw allow 443/tcp’ and reload policy as needed.

Solution – Alternative Approaches

Use app profiles, interface-scoped rules, or temporary logging with ‘ufw logging on’ for tracing.

Verification & Acceptance Criteria

Remote connection succeeds from authorized sources while unauthorized traffic remains blocked.

Rollback Plan

Delete new rule by number and restore previous ufw backup if policy broadening was excessive.

Prevention & Hardening

Maintain firewall as code, review rule drift, and enforce least privilege by source CIDR.

Related Errors & Cross-Refs

Connection timed out, refused from reverse proxy, and incorrect bind to localhost only.

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

View all Ubuntu 20.04 LTS tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

ufw man page, Ubuntu firewall documentation, and nftables/iptables relationship notes.