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
Running supervisor behind reverseproxy #318
Comments
I don't think supervisor has any way of mapping to a different path but check http://supervisord.org/ That said I think the issue is with the proxy config. The proxy introduces a new path prefix |
The trailing slash on proxypath does the same as what a rewrite would achieve. You are right though it doesn't look like supervisor has any way of editing the base path. Even trying the hack: Doesn't work as it will always send back to I don't think it can be done until the merge from 5 years ago goes through on supervisor. Supervisor/supervisor#593 Anyway it's nothing wrong with your docker image (which is great btw). I'll close this down now that i've added some more information in case anyone else has this issue. |
Like I said, the issue is not with supervisor, the issue is with your proxy config. I just tested and here's an nginx config that works for me:
With the IP obviously adjusted to your environment 🙂 The buffering and removal of keep-alive header is required for the log streaming to work. The read timeout determines how long you can view the streaming log before nginx will cut the connection. To avoid any misunderstandings here's the complete file (it's just the default.conf from the standard nginx container with that
which I ran like so:
And works just fine. I'm able to restart/start/stop services and tail the growing stdout/stderr logs: Hope this helps. |
You are right! The buffering off made all the difference. Today i learnt. Thank you! |
Hi I've got supervisor running behind a reverse proxy using the following:
Which kind of works however when you click any task in supervisor the relative path obviously doesn't have /valheim on it so never redirects back.
I've looked in the docker container and can see the supervisor scripts under /usr/local but can't see any config or how i would alter the relative urls.
Any idea on how i could achieve this?
The text was updated successfully, but these errors were encountered: