You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've got most of the rsync reconfigured to copy just the /dist folder and do all the linking, etc. but when I run pm2 start /srv/apps/ec2/current/server/app.js (https://github.com/Unitech/pm2) or node /server/app.js I get:
events.js:72
throw er; // Unhandled 'error' event
^
Error: connect EACCES
at errnoException (net.js:904:11)
at Object.afterConnect [as oncomplete] (net.js:895:19)
Assuming this is an issue with the port or the ip address that is getting set in the configuration? I want the server to listen on 127.0.0.1:9000 for the proxy.
I can start the app by just copying it to my instance, and running grunt serve:dist so I no it's not a conflict, etc.
Any advice on how I can configure the config and call the commands to appropriately start the server in production mode?
The text was updated successfully, but these errors were encountered:
So after giving up on running my app on Heroku or Openshift due to errors: #796 & #766
I've been working on deploying on ec2 w/ and running behind an NGINX proxy - using a fork of: https://github.com/bevacqua/grunt-ec2
I've got most of the
rsync
reconfigured to copy just the/dist
folder and do all the linking, etc. but when I runpm2 start /srv/apps/ec2/current/server/app.js
(https://github.com/Unitech/pm2) ornode /server/app.js
I get:Assuming this is an issue with the port or the ip address that is getting set in the configuration? I want the server to listen on
127.0.0.1:9000
for the proxy.I can start the app by just copying it to my instance, and running
grunt serve:dist
so I no it's not a conflict, etc.Any advice on how I can configure the config and call the commands to appropriately start the server in
production
mode?The text was updated successfully, but these errors were encountered: