-
Notifications
You must be signed in to change notification settings - Fork 989
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
A fix for running newsblur behind an NGINX proxy #1828
Comments
I got to the same point and it seems like Have you managed to find the solution? Im really starting to doubt if newsblur is the right choice after seeing how the config, deployment and IoC is handled. Its actually surprising it works at all... |
Well for me that proxy fix (noted above) works great. I'm not happy with having to do it that way, but it's working great. And, newsblur is fantastic in so many ways with so much functionality that it feels like a little thing. |
Are you hitting this line: NewsBlur/docker/haproxy/haproxy.docker-compose.cfg Lines 39 to 41 in ed1a2c4
|
I'm assuming yes |
I want to run newsblur behind an nginx proxy. I've been struggling to do this.
It endlessly redirects when I hit the site in browser, incorrectly sending me to the http site again, which loops. But, curl from the docker host machine (hitting localhost) works on http and returns the content. Nginx does not work from a remote proxy machine.
The simple fix is to specify localhost in the proxy header:
But, I suspect this is not the correct way to do it. I wanted to file this bug to further discussion.
Here is what I did:
bash ./utils/custom_domain.sh mycustomdomainzzzzzzzz.com
script./usr/bin/security
) are no longer needed in generating certs.I suspect there is something (perhaps in the python code?) that determines the server is answering on http (which is correct because I'm pointing to the http service) and then assumes (wrongly in this case) that it should issue a redirect to HTTPS, but it isn't doing that correctly. IMHO.
When I use curl -vvv http://mycustomdomainzzzzzzzzzz.com/ (from the proxy machine) it always issues a 302 back to the http service, not HTTPS.
But, hitting the server from the docker host using localhost does respond correctly with the NewsBlur HTML.
Interesting headers in there...
Here is the nginx configuration:
Here is the diff from NewsBlur:master.
The text was updated successfully, but these errors were encountered: