I am running my MEAN stack on a new Fedora droplet. I seem to have the same problem as described in https://www.digitalocean.com/community/questions/connection-timeout-on-node-js-app.
The interesting thing is that it was working after creating the droplet, but stopped about 24hrs after creation of the droplet.
$ node -v gives a result, ping and tracert to my IP work, curl however does not.
I tried a simple http-server ($ npm install http-server), same result (ports open, ping working): Starting up http-server, serving ./ Available on: http://127.0.0.1:8080 http://220.127.116.11:8080 http://10.19.0.5:8080 [root@fedora-512mb-fra1-01 ~]# sudo netstat -ntlp Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 127.0.0.1:27017 0.0.0.0:* LISTEN 19235/mongod tcp 0 0 0.0.0.0:8080 0.0.0.0:* LISTEN 28920/node tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 996/sshd tcp6 0 0 :::22 :::* LISTEN 996/sshd
Pinging 18.104.22.168 with 32 bytes of data: Reply from 22.214.171.124: bytes=32 time=29ms TTL=54 Reply from 126.96.36.199: bytes=32 time=27ms TTL=54 Reply from 188.8.131.52: bytes=32 time=26ms TTL=54 Reply from 184.108.40.206: bytes=32 time=47ms TTL=54
curl: (7) Failed to connect to 220.127.116.11 port 8080: Timed out
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.
Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.
Click below to sign up and get $100 of credit to try our products over 60 days!