[GH-ISSUE #997] Custom Nginx Configuration - set_proxy_header not being respected #837

Closed
opened 2026-02-26 06:34:37 +03:00 by kerem · 2 comments
Owner

Originally created by @focher on GitHub (Apr 3, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/997

I am proxying a server that requires basic HTTP authentication. I've added the following to the Custom Nginx Configuration.

proxy_set_header Authorization "Basic dXNlcm5hbWU6cGFzc3dvcmQ=";
(this is just "username:password" already encoded with base64)

  1. If I have not enabled an Access List (Public), it passes the header with credentials fine.
  2. If I enable an Access List, it passes the credentials from the Access List but not the ones set in the proxy_set_header.

From the documentation I found, the proxy_set_header is where I should be able to set the authorization header that contains the login credentials for the proxied host.

Originally created by @focher on GitHub (Apr 3, 2021). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/997 I am proxying a server that requires basic HTTP authentication. I've added the following to the Custom Nginx Configuration. `proxy_set_header Authorization "Basic dXNlcm5hbWU6cGFzc3dvcmQ=";` (this is just "username:password" already encoded with base64) 1. If I have not enabled an Access List (Public), it passes the header with credentials fine. 2. If I enable an Access List, it passes the credentials from the Access List but not the ones set in the proxy_set_header. From the documentation I found, the proxy_set_header is where I should be able to set the authorization header that contains the login credentials for the proxied host.
kerem 2026-02-26 06:34:37 +03:00
  • closed this issue
  • added the
    stale
    bug
    labels
Author
Owner

@github-actions[bot] commented on GitHub (Mar 14, 2024):

Issue is now considered stale. If you want to keep it open, please comment 👍

<!-- gh-comment-id:1996245639 --> @github-actions[bot] commented on GitHub (Mar 14, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:
Author
Owner

@github-actions[bot] commented on GitHub (Apr 26, 2025):

Issue was closed due to inactivity.

<!-- gh-comment-id:2831741937 --> @github-actions[bot] commented on GitHub (Apr 26, 2025): Issue was closed due to inactivity.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nginx-proxy-manager-NginxProxyManager#837
No description provided.