Skip to content

I typo'd my SSH port and locked myself out for a week

General Discussion by bellaauc 1 replies 159 views
#1

So I was hardening a fresh box over at Contabo (https://contabo.com/en/vps/) and decided to move SSH off 22. Typed 22222 in sshd_config, restarted, logged out to test... and realized my client was still pointing at 2222. No out-of-band console on this plan. Took me a full week to swallow my pride and open a ticket.

The worst part? I had just set up automated backups that morning. Did I test my restore? 😊 No. No I did not.

3-2-1 rule, friends. Three copies, two media, one offsite. And maybe write down which ridiculous port you actually picked.

Anyone else done something this spectacularly self-inflicted?

3-2-1 or you're already dead
#2
bellaauc said:
Anyone else done something this spectacularly self-inflicted?

I believe I have you beat. I once configured a firewall on a OVHcloud instance in Singapore via an SSH session; I applied the ruleset before adding the allow for my own IP. The route via Tokyo adds 12ms normally, but in this case it added infinity. I had to fly there for a conference two weeks later and recovered it in person.

conbini > datacenter snacks

Post a reply

You need an account to reply. Log in or register to join the conversation.

Post reply Preview Save draft