Ubuntu 18.04 SSH connection refused after reboot

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

Remote administration fails because SSH port is unreachable.

Environment & Reproduction

After reboot, client receives connection refused or timeout responses.

Root Cause Analysis

sshd not started, firewall rules changed, or listen address misconfiguration blocks access.

Quick Triage

Verify server network reachability and local SSH daemon status.

Step-by-Step Diagnosis

Run systemctl status ssh, ss -tulpn | grep :22, and review auth/syslog entries.

Solution – Primary Fix

Enable and start ssh service, correct sshd_config listen settings, and allow firewall rule.

Solution – Alternative Approaches

Use console access to restore network and firewall baseline if remote access is fully blocked.

Verification & Acceptance Criteria

SSH connects successfully from authorized clients after reboot.

Rollback Plan

Restore prior sshd_config backup and known-good firewall policy.

Prevention & Hardening

Monitor SSH service health and validate remote access after maintenance changes.

Related Errors & Cross-Refs

Can coincide with DNS, routing, or host key mismatch warnings.

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

Refer to OpenSSH server administration and Ubuntu service management docs.