-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
using reverse proxy #1
Comments
It appears to work like this:
Running tailon: Running nginx: Can be accessed with http://localhost:8084/ If you want a subfolder you need a rewrite rule.
Means that http://localhost:8084/tailon/ works. |
In your case you properly need a rule like: |
Thanks! I'm going to give it a try and will let you know how it worked out. |
This is almost working. I tries both rewrite rules. The first one doesn't work with the second one I only GET http://sago_proxy/logs/ws/info?t=1467136255761 404 (Not Found) server {
} |
It should be noticed that you can also start with a different mount dir like this: I would not normally recommend this road as I believe the proxy should hide these details but it is an option. |
Hi,
Did you try to get this container running behind an reverse proxy (apache or nginx). I just can't get this to work (keep getting 404's).
I found this on the tailon website but it is not working. Perhaps it is because it;s running inside docker container?
location /tailon/ws {
proxy_pass http://localhost:8888/tailon/ws;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
}
Regards,
Peter
The text was updated successfully, but these errors were encountered: