Improved self-host NGINX config example#1
Open
dries007 wants to merge 1 commit intokservices:masterfrom
dries007:patch-1
Open
Improved self-host NGINX config example#1dries007 wants to merge 1 commit intokservices:masterfrom dries007:patch-1
dries007 wants to merge 1 commit intokservices:masterfrom
dries007:patch-1
Conversation
Added some proxy headers to the NGINX config example. This allows the web interface to function when self-hosting.
|
Ahh, you are a live saver!!!! I was stuck for days at the last step where the auth page would always redirect to HTTP and spent days trying to figure it out how to solve this until I saw your post. Here is my full Nginx config file if it helps for anyone else: |
Author
|
Thanks. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
While evaluating the viability of a self-hosted instance of gBridge, I came across this minor thing with the documentation.
Adding these headers allows the docker Apache to know the actual hostname and origin IP.
This is required for the proper redirection of the browser, such as when logging in to the web interface.
I'd also like to mention the screenshots are out of date, but they are still easy enough to follow along with that I don't think it's worth the effort to update them.
Kind regards,
Dries Kennes
EDIT: This doesn't completely fix the situation if HTTPS is used, because it seems the web interface/apache is hardcoded to generate HTTP urls.
This configuration allows logging in via the web interface:
(Logging in via account linking is still an issue.)