sudo netstat -plutndo you see an instance of openssh/a program listening on port 22 there?
I Had the same issue, but with the
sudo netstat -plutn | grep 22
i realized that my real port was changed to 2500, and not 22 anymore.
but now it's working properly.
I'm having the exact same problem since a letsencrypt certificate expired not connection to port 22
what do I do as I cannot access via console either....
I have solved this issue by unchecking the SSH key.
I have set an ssh key for the previous droplet. When I try to use the same ssh key for the new droplet it refused me to connect on port 22. I destroyed and created a new droplet and did not choose the ssh key. When I got the e-mail for the password it worked using that password.