Debian 10 – SSH login denied after hardening changes

📖 ~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 administrative access is blocked, delaying incident response and operations.

Environment & Reproduction

Typically follows sshd_config edits, key permission changes, or PAM policy updates.

Root Cause Analysis

Authentication policy mismatch, invalid key ownership, or disabled login methods prevents access.

Quick Triage

Use console access to inspect sshd logs and effective settings.

Step-by-Step Diagnosis

Validate user key files, permissions, and auth method directives.

Solution – Primary Fix

Restore safe sshd settings, correct key permissions, and restart ssh service.

Solution – Alternative Approaches

Use temporary console-only rollback profile when immediate access recovery is required.

Verification & Acceptance Criteria

SSH authentication succeeds for approved users with intended methods only.

Rollback Plan

Revert to previously working sshd_config if policy changes break production access.

Prevention & Hardening

Test sshd config in staging and retain out-of-band console access.

Related Errors & Cross-Refs

Related logs include Permission denied (publickey) and User not allowed because not listed in AllowUsers.

Related tutorial: View the step-by-step tutorial for Debian 10.

View all Debian 10 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

OpenSSH server configuration and Debian secure access guides.