Question
can't connect through SSh to my droplet, can't access website hosted on droplet
- Posted on April 1, 2016
- LAMP StackDigitalOceanUbuntu
Asked by kmelkon
Hello guys!
I’ve been using this droplet for about 3-4 months, and today all of a sudden I can’t connect through SSH, it just times out. I try to visit the wordpress website hosted on it, it times out, tried accessing the web console, it worked, tried connecting to localhost through ssh from web console and it worked, I also tried pinging its IP address ( 178.62.122.215 ) from my PC and I got this
--- 178.62.122.215 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3024ms
I don’t know what to do, any ideas? any information I need to provide so you can help me?
Thanks
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.
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and SMBs
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
Get our newsletter
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
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.
Seems like it is a firewall issue.
I disabled the iptables firewall using the Flush All, Delete All Chains & Accept section of the tutorial below, and that did the trick for me:
sudo iptables -P INPUT ACCEPT sudo iptables -P FORWARD ACCEPT sudo iptables -P OUTPUT ACCEPT
sudo iptables -t nat -F sudo iptables -t mangle -F sudo iptables -F sudo iptables -X
https://www.digitalocean.com/community/tutorials/how-to-list-and-delete-iptables-firewall-rules
Regards
New Year
Same Issue
BUMP!
Are there any answers for this? I’ve just experienced a similar issue and after I logged in using the web console it was suddenly working.