-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Write a UI reverse proxy guide #6410
Comments
Related to #6413 |
Hey there Since this issue hasn't had any activity in a while - we're going to automatically close it in 30 days. If you're still seeing this issue with the latest version of Nomad, please respond here and we'll keep this open and take another look at this. Thanks! |
This guide was published today! https://learn.hashicorp.com/nomad/operating-nomad/nginx-reverse-proxy It also goes over WebSocket details required to proxy the new remote exec capability of the UI. |
Hi @DingoEatingFuzz , would it be possible to host it in a subdirectory within the proxy? BUT, On my specific case I would host it under '/Nomad/'.... I tried but it did not worked... The UI ends up redirection(307) for a /ui/ instead of /Nomad/ui/ |
Unfortunately you are not missing something 😞 For the time being the UI is hardcoded to expect the |
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues. |
It is common to put the Web UI behind some sort of proxy, but given the various ways that the Web UI interacts with the network, this is easier said than done.
We should write a guide that talks through all the subtleties of what the Web UI is doing, including:
Additionally, it would be nice to provide example configs for common tools such as nginx.
There are just a lot of details to figure out in the dark.
The text was updated successfully, but these errors were encountered: