Report this

What is the reason for this report?

Troubleshooting Forever and Node.JS port

Posted on March 20, 2014

I’m using Forever to start a Node.JS app which should be listening on a specific port (4567). However, when I start the app, the port is never opened and does not show up in the output of nmap or netstat and nothing is being written to syslog about it.

I’ve looked at possible clues that I know that could help solve this, but nothing has worked. Anybody has any ideas what could be causing the port to not open after I start the app. The apps config file is shown below.

<pre> { “base_url”: “http://site.com”, “port”: “4567”, “use_port”: true, “secret”: “secret”, “bind_address”: “0.0.0.0”, “database”: “redis”, “redis”: { “host”: “127.0.0.1”, “port”: “6379”, “password”: “secret3”, “database”: “0” }, “bcrypt_rounds”: 12, “upload_path”: “uploads”, “relative_path”: “” } </pre>



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.

Sounds like your app is crashing. Check forever’s log file, does it contain any errors?

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.