Access Lists cant be edited and not working as intended

[techteam-pro-discount]

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

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

[lastsamurai26]

Should be the same like my case https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4101

[towerplease]

Got the same issue.

The Access-List-Feature is technically a mess at the current state....

Further more:

When you want to add multiple Users, everytime you click "Add" all newly entered Users are cleared...

[EvilrootNix]

Same issue, the only way is delete and create it again. I can't edit ACL

[techteam-pro-discount]

dont want to make any advertisement, but for the time beeing i switched to zoraxy proxy manager. until the acl are fixed npm lost me as a user, its way to much hassle

[Lawlietr]

This issue it's very weird for me The acl that has been established still works normally The newly created acl does not work

[oliverst78]

Same issue here... no matter if "satsify any" is on or not - in the proxy-host conf you will always find:

# Access checks must...
     satisfy all;