Forever works locally but not on AWS server

[ThoseGuysInTown]

sudo node liveApp.js works as normal
forever start -a app.js works normally and the only difference between app.js and liveApp.js is that app.js is on port 3000.

When I'm trying to do forever start -a app.js:

myserver/project$ forever start -a liveApp.js
warn:    --minUptime not set. Defaulting to: 1000ms
warn:    --spinSleepTime not set. Your script will exit if it does not stay up for at least 1000ms
info:    Forever processing file: liveApp.js

myserver/project$ forever list
info:    Forever processes running
data:        uid  command             script     forever pid  id logfile                        uptime  
data:    [0] RX9S /usr/local/bin/node liveApp.js 8903    8909    /home/ubuntu/.forever/RX9S.log STOPPED 

Sometimes the forever process will show in forever list and not work when I send http calls to the server and sometimes in won't show up and will work when sending http calls to the server.

Please help! I have no idea what the difference that is causing the issue might be. :(

[markstos]

This appears to be a support request, not a bug report, and this issue can be closed. There was likely some environment difference here, such as different versions of forever, AWS Security group rules, different handling of privileged vs non-privileged ports, Mac vs Linux.

If you are running Ubuntu 16.04 on the remote server, you consider using systemd to manage the Node.js processes instead:

https://www.axllent.org/docs/view/nodejs-service-with-systemd/

systemd is already built into Ubuntu, can make sure the services are started at boot and automatically restart if the fail. You can check on the app status with systemctl status app instead of forever list.