[GH-ISSUE #3669] Enable Individual auth_basic Configuration for Different Locations within the Same Site in Nginx Proxy Manager #2430

Open
opened 2026-02-26 07:35:32 +03:00 by kerem · 2 comments
Owner

Originally created by @pwddd on GitHub (Apr 1, 2024).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3669

Is your feature request related to a problem? Please describe.
I encountered an issue when using auth_basic for access control in Nginx Proxy Manager, as it can conflict with application-level Auth since they both use the same request header. Therefore, I would like to propose a new feature that allows for configuring auth_basic separately for each location block. This would enable disabling auth_basic for specific locations.

Describe the solution you'd like
I would like the ability to configure auth_basic at the location level in Nginx Proxy Manager. This means having the option to disable auth_basic for specific location blocks while leaving it enabled for others.

Describe alternatives you've considered
One alternative is to manually modify the Nginx configuration files generated by Nginx Proxy Manager, but this is not ideal as it requires manual intervention and may be overwritten by configuration changes in Nginx Proxy Manager.

Additional context
This feature would provide more flexibility in access control configurations for users of Nginx Proxy Manager, especially in scenarios where auth_basic conflicts with application-level authentication mechanisms.

Originally created by @pwddd on GitHub (Apr 1, 2024). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3669 <!-- Are you in the right place? - If you are looking for support on how to get your upstream server forwarding, please consider asking the community on Reddit. - If you are writing code changes to contribute and need to ask about the internals of the software, Gitter is the best place to ask. - If you think you found a bug with NPM (not Nginx, or your upstream server or MySql) then you are in the *right place.* --> **Is your feature request related to a problem? Please describe.** I encountered an issue when using auth_basic for access control in Nginx Proxy Manager, as it can conflict with application-level Auth since they both use the same request header. Therefore, I would like to propose a new feature that allows for configuring auth_basic separately for each location block. This would enable disabling auth_basic for specific locations. **Describe the solution you'd like** I would like the ability to configure auth_basic at the location level in Nginx Proxy Manager. This means having the option to disable auth_basic for specific location blocks while leaving it enabled for others. **Describe alternatives you've considered** One alternative is to manually modify the Nginx configuration files generated by Nginx Proxy Manager, but this is not ideal as it requires manual intervention and may be overwritten by configuration changes in Nginx Proxy Manager. **Additional context** This feature would provide more flexibility in access control configurations for users of Nginx Proxy Manager, especially in scenarios where auth_basic conflicts with application-level authentication mechanisms.
Author
Owner

@github-actions[bot] commented on GitHub (Oct 26, 2024):

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

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

@Egor3f commented on GitHub (Sep 15, 2025):

👍

<!-- gh-comment-id:3292755886 --> @Egor3f commented on GitHub (Sep 15, 2025): 👍
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#2430
No description provided.