[GH-ISSUE #4] listen on port 80 #6

New issue

Closed

opened 2026-02-26 05:31:02 +03:00 by kerem · 1 comment

kerem commented

2026-02-26 05:31:02 +03:00

Owner

Originally created by @Maxence on GitHub (Jun 29, 2011).
Original GitHub issue: https://github.com/NarrativeScience-old/log.io/issues/4

How I can listen on port 80, actually I have apache and nginx listening in port 80 with2 ip's, I got a new address ip for log.io but I don't know how I can setup my ip address or an hostname on server.conf

Originally created by @Maxence on GitHub (Jun 29, 2011). Original GitHub issue: https://github.com/NarrativeScience-old/log.io/issues/4 How I can listen on port 80, actually I have apache and nginx listening in port 80 with2 ip's, I got a new address ip for log.io but I don't know how I can setup my ip address or an hostname on server.conf

kerem closed this issue

2026-02-26 05:31:02 +03:00

kerem commented

2026-02-26 05:31:03 +03:00

Author

Owner

@msmathers commented on GitHub (Jun 30, 2011):

You need root permissions to bind node to port 80, but Log.io runs as its own logio user who doesn't have permission. You could manually run the server process as root to accomplish this:

sudo log-server

However given Log.io's almost non-existent security, I wouldn't recommend this. I'll revisit this issue in a later release, non-standard ports will suffice for now.

@msmathers commented on GitHub (Jun 30, 2011): You need root permissions to bind node to port 80, but Log.io runs as its own logio user who doesn't have permission. You could manually run the server process as root to accomplish this: sudo log-server However given Log.io's almost non-existent security, I wouldn't recommend this. I'll revisit this issue in a later release, non-standard ports will suffice for now.

kerem referenced this issue

2026-02-26 05:31:40 +03:00

[PR #6] [CLOSED] Possible race condition with append() #224

kerem referenced this issue

2026-02-26 05:31:48 +03:00

[PR #271] fix #272