You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Access Lists do not work correctly when deploying as rootless.
When defining an access list with NPM using allow <IP_ADDRESS> and then enabling a ACL within a host proxy, the ACL does not work and any IP can still access the host. However is redeployed as sudo, then the ACLs work as intended.
Nginx Proxy Manager Version
2.11.2
To Reproduce
Steps to reproduce the behavior:
Deploy NPM as rootless
Setup NPM admin account
Create an ACL
Create a proxy host and add the host to the ACL
Use an external machine to access host, verify that you can still access the host even though it should be blocked by ACL
Purge installation and redeploy as sudo
Use an external machine to access host and verify that the ACL now works and blocks access to host.
Expected behavior
ACLs should apply when deploying NPM as rootless user.
Operating System
Ubuntu server 24.04
The text was updated successfully, but these errors were encountered:
Checklist
jc21/nginx-proxy-manager:latest
docker image?Describe the bug
Access Lists do not work correctly when deploying as rootless.
When defining an access list with NPM using allow <IP_ADDRESS> and then enabling a ACL within a host proxy, the ACL does not work and any IP can still access the host. However is redeployed as sudo, then the ACLs work as intended.
Nginx Proxy Manager Version
2.11.2
To Reproduce
Expected behavior
ACLs should apply when deploying NPM as rootless user.
Operating System
Ubuntu server 24.04
The text was updated successfully, but these errors were encountered: