Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
The problem is MTU related try setting your client’s network card mtu smaller for example
ifconfig enp10s0 mtu 1000 (linux)
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