Struggling with port 80

[Lee Marshall]

Having issues running node.js because port 80 is in use. Any advice? I'm using a cloud VPS server.

[codepilot Account]

Have you tried HTTPS on port 443?

On Sat, May 30, 2015 at 3:05 PM, Lee Marshall <redliza...@gmail.com> wrote:

Having issues running node.js because port 80 is in use. Any advice? I'm using a cloud VPS server.

--
Job board: http://jobs.nodejs.org/
New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md
Old group rules: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
---
You received this message because you are subscribed to the Google Groups "nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+un...@googlegroups.com.
To post to this group, send email to nod...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/1c9077fd-8595-4ce5-9431-2f15c81ea9f2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Ryan Schmidt]

On May 30, 2015, at 5:05 PM, Lee Marshall wrote:
>
> Having issues running node.js because port 80 is in use. Any advice? I'm using a cloud VPS server.

What is port 80 in use by? Presumably by a web server provided by your VPS. If you don't need that web server for anything else, you could stop it; then you can use port 80 for something else, like node.

Alternately -- and this is what many people do -- keep a standard web server like (recommended) nginx or (if absolutely necessary) apache on port 80, and configure it as a reverse proxy to hand relevant requests on to your node app, which runs on an unprivileged port, like 3000. This is useful if you need to run multiple node web sites from one server, or if you want to also run web sites that aren't run by node. You can also configure nginx or apache to handle some of the load, for example static files, while letting your node app focus on its unique duties.

[zladuric]

Port 80 is likely in use by apache or nginx. If it's one of them, you should either bring them down and let node take port 80, or, as is usual, forward requests that you want to node running on a high port, something above 1024.