[GH-ISSUE #97] Reverse proxy issues #68

New issue

Closed

opened 2026-03-03 16:04:10 +03:00 by kerem · 4 comments

kerem commented

2026-03-03 16:04:10 +03:00

Owner

Originally created by @amirabiri-odoro on GitHub (Jul 4, 2017).
Original GitHub issue: https://github.com/mthenw/frontail/issues/97

I could not figure out how to run frontail behind an nginx reverse proxy.

I've tried the following nginx configuration:

location /logs/ {
    proxy_pass http://frontail/;
    sub_filter_once off;
    sub_filter_types text/html;
    sub_filter 'href="/' 'href="/logs/';
    sub_filter 'src="/' 'src="/logs/';
    sub_filter "io.connect('/'" "io.connect('/logs/'";
    access_log /var/log/nginx/access.log trace;
}

The assets worked, but the socket.io still tries to connect to /?E...

Is it possible to add some cmd line switch to tell frontail which url path to use?

Or even better - use relative paths for assets / socket?

Originally created by @amirabiri-odoro on GitHub (Jul 4, 2017). Original GitHub issue: https://github.com/mthenw/frontail/issues/97 I could not figure out how to run frontail behind an nginx reverse proxy. I've tried the following nginx configuration: location /logs/ { proxy_pass http://frontail/; sub_filter_once off; sub_filter_types text/html; sub_filter 'href="/' 'href="/logs/'; sub_filter 'src="/' 'src="/logs/'; sub_filter "io.connect('/'" "io.connect('/logs/'"; access_log /var/log/nginx/access.log trace; } The assets worked, but the socket.io still tries to connect to `/?E...` Is it possible to add some cmd line switch to tell frontail which url path to use? Or even better - use relative paths for assets / socket?

kerem closed this issue

2026-03-03 16:04:10 +03:00

kerem commented

2026-03-03 16:04:11 +03:00

Author

Owner

@scottbasgaard commented on GitHub (Dec 22, 2017):

Any updates on this @amirabiri-odoro? Would love to have the same setup.

@scottbasgaard commented on GitHub (Dec 22, 2017): Any updates on this @amirabiri-odoro? Would love to have the same setup.

kerem commented

2026-03-03 16:04:11 +03:00

Author

Owner

@amirabiri-odoro commented on GitHub (Dec 25, 2017):

I resorted to running on root path on a different port.

@amirabiri-odoro commented on GitHub (Dec 25, 2017): I resorted to running on root path on a different port.

kerem commented

2026-03-03 16:04:11 +03:00

Author

Owner

@carschrotter commented on GitHub (Jun 17, 2019):

Any updates on this @amirabiri-odoro? Would love to have the same setup.
replace
sub_filter "io.connect('/'" "io.connect('/logs/'"; with
sub_filter "path: '/socket.io'" "path: '/logs/socket.io'";
works fine

@carschrotter commented on GitHub (Jun 17, 2019): > > > Any updates on this @amirabiri-odoro? Would love to have the same setup. replace `sub_filter "io.connect('/'" "io.connect('/logs/'";` with `sub_filter "path: '/socket.io'" "path: '/logs/socket.io'";` works fine

kerem commented

2026-03-03 16:04:11 +03:00

Author

Owner

@scottbasgaard commented on GitHub (Jun 19, 2019):

thanks @carschrotter, will give it a go!

@scottbasgaard commented on GitHub (Jun 19, 2019): thanks @carschrotter, will give it a go!