[GH-ISSUE #2913] Unauthorized after re-enabling host #1995

Open
opened 2026-02-26 07:33:36 +03:00 by kerem · 7 comments
Owner

Originally created by @jaitaiwan on GitHub (May 12, 2023).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2913

Checklist

  • Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
    • Yes
  • Are you sure you're not using someone else's docker image?
    • No
  • Have you searched for similar issues (both open and closed)?
    • Yes

Describe the bug
403 unauthorized after re-enabling a host that has an access list.

Nginx Proxy Manager Version

To Reproduce
Steps to reproduce the behavior:

  1. Create a proxy host that is linked to an access control list.
  2. Default deny is all, allow the IP of the current client you're using to access. At this point http basic auth is requested as expected.
  3. Disable said host
  4. Navigate to host url. 404 error displayed appropriately.
  5. Enabled host
  6. Navigate to host url
  7. 403 not authorized. Expect http basic auth at this point
  8. Edit host. No changes. Click Save
  9. Navigate to host url. Http basic auth request triggers as expected

Expected behavior
After enabling the host, http basic auth is requested.

Additional context
Docker container running latest 2.10.3

Originally created by @jaitaiwan on GitHub (May 12, 2023). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2913 **Checklist** - Have you pulled and found the error with `jc21/nginx-proxy-manager:latest` docker image? - Yes - Are you sure you're not using someone else's docker image? - No - Have you searched for similar issues (both open and closed)? - Yes **Describe the bug** 403 unauthorized after re-enabling a host that has an access list. **Nginx Proxy Manager Version** <!-- What version of Nginx Proxy Manager is reported on the login page? --> **To Reproduce** Steps to reproduce the behavior: 1. Create a proxy host that is linked to an access control list. 2. Default deny is all, allow the IP of the current client you're using to access. At this point http basic auth is requested as expected. 3. Disable said host 4. Navigate to host url. 404 error displayed appropriately. 5. Enabled host 6. Navigate to host url 7. 403 not authorized. Expect http basic auth at this point 8. Edit host. No changes. Click Save 9. Navigate to host url. Http basic auth request triggers as expected **Expected behavior** After enabling the host, http basic auth is requested. **Additional context** Docker container running latest 2.10.3
Author
Owner

@Gaz492 commented on GitHub (May 12, 2023):

Having the same issue and was driving me mad thinking I was doing something wrong

<!-- gh-comment-id:1545529590 --> @Gaz492 commented on GitHub (May 12, 2023): Having the same issue and was driving me mad thinking I was doing something wrong
Author
Owner

@github-actions[bot] commented on GitHub (Jan 20, 2024):

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

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

@jaitaiwan commented on GitHub (Jan 20, 2024):

👍

<!-- gh-comment-id:1901946182 --> @jaitaiwan commented on GitHub (Jan 20, 2024): 👍
Author
Owner

@bamnoru commented on GitHub (Nov 4, 2024):

Same issue with v2.12.1

<!-- gh-comment-id:2455531298 --> @bamnoru commented on GitHub (Nov 4, 2024): Same issue with v2.12.1
Author
Owner

@adriengivry commented on GitHub (Nov 8, 2024):

Same issue with v2.12.1, cannot seem to find a workaround

<!-- gh-comment-id:2465884175 --> @adriengivry commented on GitHub (Nov 8, 2024): Same issue with v2.12.1, cannot seem to find a workaround
Author
Owner

@robinmalik commented on GitHub (Dec 22, 2024):

Facing the same issue.

<!-- gh-comment-id:2558505724 --> @robinmalik commented on GitHub (Dec 22, 2024): Facing the same issue.
Author
Owner

@github-actions[bot] commented on GitHub (Jul 13, 2025):

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

<!-- gh-comment-id:3066345394 --> @github-actions[bot] commented on GitHub (Jul 13, 2025): Issue is now considered stale. If you want to keep it open, please comment :+1:
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#1995
No description provided.