Skip to content
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

Updated to address the issue with reverse proxy setup #287

Closed
wants to merge 1 commit into from
Closed

Updated to address the issue with reverse proxy setup #287

wants to merge 1 commit into from

Conversation

thepra
Copy link

@thepra thepra commented Mar 21, 2020

{{.Host}} should be fixed and become the domain chosen if the prod setup lives behind a proxy. The Theme is messed up because points to localhost:[port]
As of now it's not part of the installation process to setup the host in a way that supports reverse proxy handling/pointing.


  • I have signed the CLA

{{.Host}} should be fixed and become the domain chosen if the prod setup lives behind a proxy. As of now it's not part of the installation process to setup the host in a way that supports reverse proxy handling/pointing
@thebaer
Copy link
Member

thebaer commented Mar 23, 2020

As mentioned in this comment, that issue was most likely caused by a configuration error instead of an application bug. Will close this for now, pending your response to my comment over on #286.

@thebaer thebaer closed this Mar 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

Setup with reverse proxy leads to some static GET to localhost:[port] instead of the root domain
2 participants