I’ve tested and you can restore access. It takes a few steps, so it’d be easier to just destroy the droplet and spin up a new one, if your situation can stand the downtime.
To restore access without destroying:
- DO web GUI > Access > Reset Root Password
- DO web GUI > Access > Console Access
- username: root
- type password emailed to you by DO (I had to type, couldn’t paste)
- It will require you to change root password
- at the prompt retype the existing password (the one emailed above)
- type new password
- retype new password
-
vim /etc/ssh/sshd_config
PermitRootLogin yes
- save and exit vim editor
service ssh restart
- add
admin_user
tousers
hash, and addkeys
(ssh keys docs) - run
server.yml
again
Then everything should be normal. I hope you’ll report back so we know what is possible and what comes up in a critical situation like this. Thanks!