Not sure if anyone needs anymore discussion on this, but I faced the same problem and got a lead from this post to fix.
Yes, I think port was blocked. When I did sudo ufw allow 22 from console and tried to connect, I was able to connect

Awesome SO I HAVE SOLVED THIS.

Login to your digital ocean account and go to launch console under access in your droplet.
then type in your username and then your password.

Once you are logged in type $ sudo ufw allow 22

Try again in your terminal and it will work. :)

Hello! I had the same problem and it persists even after enabling port 22 in the firewall.

In my case (I estimate that for having too many ssh keys) I had to initialize the ssh agent and add the key “manually”. And it worked.

The steps I followed were:

To initialize the ssh agent

eval $ (ssh-agent -s)

To add the key

ssh-add -i ~ / .ssh / key

— If your password has a paraphrase, you should insert it
— In my case, the key was in the ~ / .ssh / directory and was called “key”, check the names of your files and replace them.

To enter the Droplet via ssh

ssh -i ~ / .ssh / key root @ droplet-ip

— It is important to add the argument “-i” to the ssh command and tell it the full path where your key is located
— Then you can indicate with which user and to which IP you will connect

I hope it works for you too.

Regards

thanks a lot for : run $sudo ufw allow 22

You can check if your ssh service is running on your droplet by going to the Console Access
Also check your ssh config if you are allowed to login as root, and if you made a ssh key at the creating, you need to use that. For more information check here

Is this a fresh droplet or one you’ve connect to before?

Did you install any software? Check if you got a firewall running like ufw, iptables,Gufw etc.
Maybe the port is blocked, also check your pc if it is allowing outgoing ssh connections (port 22)

I have a few questions.

What operating system is your server?
Are you able to log in via web console with DigitalOcean?
Did you make any firewall rules - If so you may have blocked 22.

You can always try stopping the firewall service to see if that allows connection via SSH. If so you know you’ll have to add a rule.

The problem is MTU related
try setting your client’s network card mtu smaller for example

ifconfig enp10s0 mtu 1000
(linux)

I started experiencing this issue after enabling ufw using the command

sudo ufw enable

I had to disable ufw using the command:

sudo ufw disable

That’s all.

I hope this helps

sudo ufw allow 22 

did it for me