


Log in via web console and run this: netstat -tulpnĭo you see SSH? Is it on port 22? If not, try using the other port. While firewall can block ping too, I doubt you’ve done anything to block ICMP packets.

Ping the droplet, see if you get a response. Let’s break those possibilities down a bit. I can’t say for sure which or which combination, but the timeout provides a clear indication that it is not directly based on login at that stage (though #5 would imply that it was in previous errors).
