Question
no route to host on new droplet
I’m new to DO and have been struggling for the last few days to get a working droplet up and running. What typically happens is that the droplet is ‘successfully’ created and I can access it from the console on DO.com. However, if I try to ssh to it from outside of DO I get 'no route to host’; but, oddly enough, I can ping the droplet from the same system that the ssh failed on. I have an open ticket on this and periodically get a 'it should be working’ response (it usually isn’t). I want to think that this isn’t typical for DO hosting - any suggestions?
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.
×
are you using the IP address, or a domain you are pointing to that droplet?
if you are using a domain, sometimes it can take a day or two for the domain to start resolving properly across the web. In the meantime you can just use the IP they give you for that droplet.
If you are using the IP, that is unusual, unless you set it up with an alternative ssh port, or added a firewall and have all ports closed.
Can you give a little more information, like what image you used, OS, did you add ssh keys? any other clues you might think of?
Is it possible that your local network or ISP filter port 22? Have you tried setting a custom SSH port?
I can ssh from the same laptop to AWS with no problem so I don’t think it is a filtering issue.
I might try creating a droplet in a different region and see if that makes a difference. Currently working in nyc
I am attempting to use the IP to connect. I have tried two droplets one with ssh and one without (same behavior). I selected the ubuntu install in both cases. no alternate ssh port, no firewall, i would say it is a pretty generic install (which is where I like to start). [moved this from being an ‘answer’]