NginxProxyManager / NginxProxyManager/nginx-proxy-manager

Access Lists cant be edited and not working as intended

Open
#4,104 10 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
TypeScript
Stars
34.2k
Forks
3.9k
Avg merge
21h 12m
Merged PRs (30d)
20

Description

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?
    • Yes
  • Have you searched for similar issues (both open and closed)?
    • Yes

Describe the bug
When i use the Access Lists, for example: Workers and add authorization its saved for that user, if i want to edit it later, i have to not only add the new user password, but also all password for other users again (passwords arent safed).
Also even with satsify any on, i still need to add the ip/subnet 0.0.0.0/24, otherwise the access list doesnt work at all :/

Nginx Proxy Manager Version

Latest

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'Proxy Manager Webui'
  2. Click on 'Access Lists'
  3. Add a new one, add a user
  4. Save it
  5. Edit the acl again, add a new user, click save and you are prompted with an error
  6. See error

Expected behavior
Edit the ACL and have the other user passwords saved

Screenshots
1J6CS46458

Operating System
Proxmox VE, Ubuntu 24.04 Server with XFCE4 Desktop running Portainer, inside Portainer a Container for Nginx Reverse Proxy Manager

Additional context

  • None

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in the Proxy Manager WebUI's Access Lists flow and reproduce the issue by creating an ACL with one user, saving it, then editing it. Check both reported behaviors: whether existing passwords remain usable when adding a user, and whether the any-source setting works without manually adding 0.0.0.0/24. Done means editing succeeds without re-entering unchanged passwords and the any-source setting works as expected.

Written by the indexing model from the issue text.

Assessment

Tech stack
nginx, typescript
Domain
authentication, authorization, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.