By danvoell
I set up a rails app called discourse on my droplet. The IP for my droplet (107.170.129.25) was working for the first 5 or so days, now when I try to access it directly via the IP I get the following message - “Oops! Google Chrome could not connect to 107.170.129.25”
I’m not sure what happened. My droplet still shows as active. The app was working last time I checked. Could it have been hacked? Is there any way to try restarting the droplet?
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!
<pre>~: telnet 107.170.129.25 80 <br>Trying 107.170.129.25… <br>telnet: Unable to connect to remote host: Connection refused</pre> <br>Looks like your webserver crashed. You can try starting it (nginx: <code>sudo service nginx start</code>, apache: <code>sudo service apache2 start</code>) or rebooting your droplet (<code>sudo reboot</code>) which should fix it.
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.
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.