Same issue today. It looks like it's been happening for a few years based on this thread, anyone found a solid answer? :/
Yeah, I meet the same problem, the new automatic password is not working. I can only login in through the web embedded terminal. This is really frustrating!
I forget what I did before but all I know now is that whenever I try to reset the root password and login to root@(my_ip) with the newest generated password, I get the message "Permission denied, please try again".
After 3 tries, I get "Permission denied (publickey,password)" -- where do I even begin to deal with publickey?
My root password was working a month ago. Now I tried it and it says incorrect in terminal. I am surprised. Then I reset my password from droplet dashboard. It emailed me new root password. New root password is not working.
Can anyone help to find the solution? Please help.
i think the problem is the root login is disabled via console.
I lost my user password, and now cant use root to reset it, cant login with root since it is hardened.
Same problem here.
I reset password from droplet dashboard. It emailed me new root password. New root password returns "Access denied"
I can't even log in with web console getting "Server disconnected (code: 1006)" which might be something to do with my network (at a university on public internet access but I can ssh to other places without problem).
Pretty sure i disabled root ssh access in the OS. But now can't get in to change it.
I have another admin user but can't remember its user and pw either.
Any alternative to scraping the enter droplet and starting from scratch?
So this worked for me.
logged in with my sudo user (created when doing lamp walkthrough)
then used command
su - root
entered new password sent to email
set new password.
Currently in root and having no issues!
Same problem here. I opened a support ticket but the response time is horrible. Seems to be an issue that is a known problem and no one on Digital Ocean is responding in this thread. Will definitely be looking into another service after this problem.
Same problem this morning. I have a feeling it's because I disabled password based logins in my provision script... On the plus side I build it with a provision script so it's dad trivial to spin the whole stack back up.