mirror of
https://github.com/PowerDNS-Admin/PowerDNS-Admin.git
synced 2026-04-25 08:45:55 +03:00
[GH-ISSUE #59] Login does not complete behind a reverse proxy #41
Labels
No labels
bug / broken-feature
bug / broken-feature
docs / request
feature / request
help / other
mod / help-wanted
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/PowerDNS-Admin-PowerDNS-Admin#41
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @pirogoeth on GitHub (Jul 1, 2016).
Original GitHub issue: https://github.com/PowerDNS-Admin/PowerDNS-Admin/issues/59
Originally assigned to: @ivanfilippov on GitHub.
For example, my BIND_ADDRESS is
10.0.0.1, and I've got a reverse proxy serving it. When login happens and the user is redirected, for some reason, it redirects to10.0.0.1:9393. Is there a way to override this behaviour?@ivanfilippov commented on GitHub (Jul 1, 2016):
Hi @pirogoeth
My primary environment is behind an nginx proxy and it seems to work for me, can you share a little bit more about your setup?
@ngoduykhanh commented on GitHub (Jul 2, 2016):
I works fine for me with setup of PowerDNS-Admin+Nginx (as reverse proxy). From my experience, this might caused by the nginx config, can you share your setting?
@pirogoeth commented on GitHub (Jul 5, 2016):
Sorry for the delay -- here's my nginx config:
And here's my config.py for powerdns-admin:
@ivanfilippov commented on GitHub (Jul 13, 2016):
@pirogoeth
Sorry for delay. I've replicated your issue, to fix it add the below line to your
location /block.proxy_set_header Host $host;@pirogoeth commented on GitHub (Jul 13, 2016):
@ivanfilippov Not sure how I missed that / including proxy_params. Fixed, thanks!
@davekempe commented on GitHub (Sep 15, 2022):
For the benefit of others, I had this problem, and it turned out the time was wrong on the pdns-admin server (running flask). The haproxy in front of it meant the session didn't work, I got a 403 immediately.
So, if you get this error, check all the servers have the right time!