Developer Closes Public SSH Port After Hours-Long Lockout on Production Server
A developer was locked out of their own production server for several hours due to two overlooked issues: Ubuntu cloud images default to the 'ubuntu' user rather than 'root' in rescue consoles, and the ubuntu account was locked since provisioning. Separately, direct SSH connections were timing out — likely due to a rotating home IP — though the issue resolved itself once the IP changed. To recover access, the developer used the hosting panel's emergency rescue mode, chrooting into the real disk to unlock the account and reset credentials safely. As a long-term fix, Tailscale was installed to route admin access over a stable private IP, eliminating dependence on a fluctuating public IP. Public port 22 was then closed entirely, with SSH now accessible only through the Tailscale network.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in