Stop getting locked out when testing your SSH config
SSH & Remote Administration
Stop getting locked out when testing your SSH config
🧩 The Challenge
Everyone has been there, messing with sshd_config only to realize after you hit save that you accidentally nuked your own ability to get back in. You end up staring at a hung terminal, praying you left a different window open somewhere else.
💡 The Fix
Use the test flag before restarting the service to make sure your syntax is actually valid. It saves you from that sinking feeling of being locked out of a production box because of a stray character.
sshd -t && systemctl reload sshd
⚙️ Why It Works
Running the binary with the test flag parses the configuration file for errors without actually applying the changes to the running daemon. It acts as a safety net, letting you catch typos like a missing semicolon or a non-existent group before they cause a production outage.
🚀 Pro-Tip: Always keep one existing SSH session open while you test, or you are just asking for a frantic trip to the physical console.
Linux Tips & Tricks | © ngelinux.com | 11/5/2026
