route behind reverse proxy #126

New issue

Open

opened 2026-02-26 05:31:24 +03:00 by kerem · 2 comments

kerem commented

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

Owner

Originally created by @radmanz on GitHub (Apr 21, 2015).
Original GitHub issue: https://github.com/NarrativeScience-old/log.io/issues/153

Due to the geographic location of my server, i'm unable to open any ports other then 80,443 to bypass this problem.
I currently have a socket.io application running on this server, and would like to use log.io to view the existing application log files.
I am able access log.io's http server using NGINX reverse proxy. (using this method: https://github.com/NarrativeScience/Log.io/issues/142 )

But the socket.io route is conflicting with the existing socket.io application.
Whats the best way to change the socket.io resource: / path: on both the server and client of log.io?
I've done some experimentation and managed to change the client browser JS path from log.io.js, but im not sure if this is the best method?
Any information would be appreciated.

Originally created by @radmanz on GitHub (Apr 21, 2015). Original GitHub issue: https://github.com/NarrativeScience-old/log.io/issues/153 Due to the geographic location of my server, i'm unable to open any ports other then 80,443 to bypass this problem. I currently have a socket.io application running on this server, and would like to use log.io to view the existing application log files. I am able access log.io's http server using NGINX reverse proxy. (using this method: https://github.com/NarrativeScience/Log.io/issues/142 ) But the socket.io route is conflicting with the existing socket.io application. Whats the best way to change the socket.io resource: / path: on both the server and client of log.io? I've done some experimentation and managed to change the client browser JS path from log.io.js, but im not sure if this is the best method? Any information would be appreciated.

kerem added the

planned feature

feature request

labels

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

kerem commented

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

Author

Owner

@strannik19 commented on GitHub (Mar 15, 2017):

would be great if the log_server.conf conf file has something like:
url_prefix: 'logio'
so that the url can be accessed as http://127.0.0.1:28777/logio
which would make life much more easier for proxying.

@strannik19 commented on GitHub (Mar 15, 2017): would be great if the log_server.conf conf file has something like: `url_prefix: 'logio'` so that the url can be accessed as http://127.0.0.1:28777/logio which would make life much more easier for proxying.

kerem commented

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

Author

Owner

@sik0vny commented on GitHub (May 10, 2020):

I agree with strannik19

@sik0vny commented on GitHub (May 10, 2020): I agree with strannik19