starred/peerflix-server

Fork 0

mirror of https://github.com/asapach/peerflix-server.git synced 2026-04-25 14:45:50 +03:00

[GH-ISSUE #87] running on 80 port #288

New issue

Closed

opened 2026-03-15 02:52:00 +03:00 by kerem · 11 comments

kerem commented

2026-03-15 02:52:00 +03:00

Owner

Originally created by @salientnet on GitHub (Nov 7, 2016).
Original GitHub issue: https://github.com/asapach/peerflix-server/issues/87

Hi,

I am using the peerflix-server app now and it is working well.
But I want to run on 80 port.
Could do you explain about it?

Thanks,
Salient

Originally created by @salientnet on GitHub (Nov 7, 2016). Original GitHub issue: https://github.com/asapach/peerflix-server/issues/87 Hi, I am using the peerflix-server app now and it is working well. But I want to run on 80 port. Could do you explain about it? Thanks, Salient

kerem

2026-03-15 02:52:00 +03:00

closed this issue
added the
question
label

kerem commented

2026-03-15 02:52:15 +03:00

Author

Owner

@asapach commented on GitHub (Nov 7, 2016):

You can set PORT environment variable like so (in bash):

PORT=80; peerflix-server

But then you'll need to run it under root or sudo (because ports under 1024 are restricted), and I would not recommend it, because it's a potential security vulnerability.

Instead I would recommend setting up a reverse proxy server like nginx or apache to proxy the traffic from peerflix-server.

@asapach commented on GitHub (Nov 7, 2016): You can set `PORT` environment variable like so (in bash): ``` sh PORT=80; peerflix-server ``` But then you'll need to run it under root or sudo (because ports under 1024 are restricted), and I would not recommend it, because it's a potential security vulnerability. Instead I would recommend setting up a reverse proxy server like nginx or apache to proxy the traffic from peerflix-server.

kerem commented

2026-03-15 02:52:21 +03:00

Author

Owner

@salientnet commented on GitHub (Nov 8, 2016):

Thanks for your help, but I tried and it is not working yet.

@salientnet commented on GitHub (Nov 8, 2016): Thanks for your help, but I tried and it is not working yet.

kerem commented

2026-03-15 02:52:26 +03:00

Author

Owner

@salientnet commented on GitHub (Nov 8, 2016):

Hi asapach,

I can run the app with port 80 now.
And i want to run the app as grunt with persistence
could you help me about it?

Thanks,
Salient

@salientnet commented on GitHub (Nov 8, 2016): Hi asapach, I can run the app with port 80 now. And i want to run the app as grunt with persistence could you help me about it? Thanks, Salient

kerem commented

2026-03-15 02:52:31 +03:00

Author

Owner

@asapach commented on GitHub (Nov 8, 2016):

What do you mean by running it as grunt? What kind of persistence do you have in mind?

@asapach commented on GitHub (Nov 8, 2016): What do you mean by running it as grunt? What kind of persistence do you have in mind?

kerem commented

2026-03-15 02:52:36 +03:00

Author

Owner

@salientnet commented on GitHub (Nov 8, 2016):

i think the app is running with grunt serve command to customize.
Otherwise it is running with peerflix-server.
Now if i run the grunt serve and the command end, the app is not running.
Could i execute it continuously?

@salientnet commented on GitHub (Nov 8, 2016): i think the app is running with grunt serve command to customize. Otherwise it is running with peerflix-server. Now if i run the grunt serve and the command end, the app is not running. Could i execute it continuously?

kerem commented

2026-03-15 02:52:41 +03:00

Author

Owner

@asapach commented on GitHub (Nov 8, 2016):

You should not be running it via grunt. This is only for development mode. You should install it globally: npm install -g peerflix-server and run it as a daemon: https://github.com/asapach/peerflix-server#daemon
To run it continuously use forever: https://github.com/foreverjs/forever

@asapach commented on GitHub (Nov 8, 2016): You should not be running it via grunt. This is only for development mode. You should install it globally: `npm install -g peerflix-server` and run it as a daemon: https://github.com/asapach/peerflix-server#daemon To run it continuously use `forever`: https://github.com/foreverjs/forever

kerem commented

2026-03-15 02:52:46 +03:00

Author

Owner

@salientnet commented on GitHub (Nov 8, 2016):

yeah, but I changed some html and it didn't implement when i run the with peerflix-server.

@salientnet commented on GitHub (Nov 8, 2016): yeah, but I changed some html and it didn't implement when i run the with peerflix-server.

kerem commented

2026-03-15 02:52:51 +03:00

Author

Owner

@asapach commented on GitHub (Nov 8, 2016):

OK, instead of running grunt server you should just be able to run <path to peerflix-server>/server/bin.js, and then you should be able to use it with forever

@asapach commented on GitHub (Nov 8, 2016): OK, instead of running `grunt server` you should just be able to run `<path to peerflix-server>/server/bin.js`, and then you should be able to use it with `forever`

kerem commented

2026-03-15 02:52:56 +03:00

Author

Owner

@salientnet commented on GitHub (Nov 8, 2016):

could you teach me in more details?

@salientnet commented on GitHub (Nov 8, 2016): could you teach me in more details?

kerem commented

2026-03-15 02:53:01 +03:00

Author

Owner

@varunchopra commented on GitHub (Dec 29, 2016):

Running it with with forever doesn't lead to anything unfortunately. Page doesn't load.

@salientroot Run this,

npm install -g forever

forever start $(which peerflix-server)

@varunchopra commented on GitHub (Dec 29, 2016): Running it with with `forever` doesn't lead to anything unfortunately. Page doesn't load. @salientroot Run this, ```npm install -g forever``` ```forever start $(which peerflix-server)```

kerem commented

2026-03-15 02:53:06 +03:00

Author

Owner

@asapach commented on GitHub (Dec 30, 2016):

@chopraaa, works fine for me. Enable the logs and see if there are any errors: https://github.com/foreverjs/forever#command-line-usage (I'd rather create a separate issue if there are.)

Having said that, I still don't recommend running it on port 80 directly.

@asapach commented on GitHub (Dec 30, 2016): @chopraaa, works fine for me. Enable the logs and see if there are any errors: https://github.com/foreverjs/forever#command-line-usage (I'd rather create a separate issue if there are.) Having said that, I still don't recommend running it on port 80 directly.