Be the first user to complete this post
|Add to List|
Resolved - Error: listen eaccess using nodejs and pm2
I bumped into this issue when trying to run my node application using pm2. From my understanding, a combination of the following factors causes the issue
- pm2 usually needs to be installed globally, which means more than likely you installed it using sudo. Therefore you need sudo to run the command itself.
- If your node application needs to listen on port 80, you're gonna need root access.
Once you are root, you might realize that you need to install node/nvm as well in the root user as well in case it wasn't installed already.
NOTE: I don't personally endorse letting nodejs listen on port 80. You're better off setting up NGINX to listen on port 80 which forwards requests to your node process which actually listens on another port. If you're not sure how to set that up, you will find this post helpful.
- Setup nginx with multi domain websites running on nodejs
- Resolved - /usr/bin/env: node: No such file or directory
- nodejs: generate uuid / guid
- Configure The 'script' tag In package.json To Run Multiple Commands
- Troubleshooting: Fatal error: watch ENOSPC on grunt watch
- set the default node version using nvm
- Testing promise sequence using mocha, chai, chai-as-promised, sinon
- Resolved - sudo npm command not found