Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ACLs does not work when using rootless #3738

Open
trulow opened this issue May 3, 2024 · 1 comment
Open

ACLs does not work when using rootless #3738

trulow opened this issue May 3, 2024 · 1 comment
Labels

Comments

@trulow
Copy link

trulow commented May 3, 2024

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
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

  1. Steps to reproduce the behavior:
  2. Deploy NPM as rootless
  3. Setup NPM admin account
  4. Create an ACL
  5. Create a proxy host and add the host to the ACL
  6. Use an external machine to access host, verify that you can still access the host even though it should be blocked by ACL
  7. Purge installation and redeploy as sudo
  8. 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

@trulow trulow added the bug label May 3, 2024
@bluekitedreamer
Copy link

Check to see if the allow directive is being added to the individual proxy host config files, those are stored at /data/nginx/proxy_host/

it would look like

allow [ip address here];

I had to change a few things to get the templating to work correctly. Likely an issue with default user of container

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants