If you can’t login to console, short of submitting a support ticket and seeing if they can help get you back in, you would effectively be locked out and would need to deploy a new Droplet. You could then create a new user and we can walk through the setup, We can then work on setting up SSH Keys after though the best way to setup SSH Keys is actually to deploy them when you deploy your Droplet (as this makes it easier). Getting you back in is what’s important right now. You could then reset passwords using passwd, such as: passwd username If you can login to console, you can re-enable PasswordAuthentication by modifying: /etc/ssh/sshd_configĪnd then restarting SSHD: service sshd restart If you never received a password and your Droplet is setup with SSH Keys only, there’s very little that can be done at this point, unfortunately, as you can’t use SSH Keys to login to the console. To login to console, you’ll need your root user password. If you can’t login to SSH, the only other way to login to your Droplet is using console, which you’d access by clicking on the name of the droplet and then clicking on ‘Access’ and then 'Launch Console’. So let’s start with not able to login with either user.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |