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?
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!
This comment has been deleted
“Is it possible that your local network or ISP filter port 22? Have you tried setting a custom SSH port?”
+1 for this. You will want to do that anyway.
to change port:
sudo nano /etc/ssh/sshd_config
You will see the place where it says the port 22…change that to whatever, then ctrl X and then:
sudo service ssh reload
Then, just to be sure, run (if your alt port was 2010):
sudo iptables -A INPUT -p tcp -d 0/0 -s 0/0 --dport 2010 -j ACCEPT
Then check your ports here: http://www.yougetsignal.com/tools/open-ports/
This comment has been deleted
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
Full documentation for every DigitalOcean product.
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
Stay up to date by signing up for DigitalOcean’s Infrastructure as a Newsletter.
New accounts only. By submitting your email you agree to our Privacy Policy
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.