IP:PORT redirect to Proxy Host

[zak-admin]

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)?
  • No

Describe the bug

After I configured proxy host yet the website is available in IP-ADDRESS:PORT. I am not sure whether my thinking is correct. Can this be a security issue.

Expected behavior

Let IP-ADDRESS:PORT redirect automatically to the relevant proxy host domain configured.

Additional context

I was using podman on debian 11

[the1ts]

I would say its not a huge security issue as it stands. However, many scans for audit purposes would say otherwise. Therefore the ports should probably be blocked from outside the docker host in these circumstances, so allowing only the NPM HTTP/HTTPS ports which do have some additional security, namely, some known attacks being blocked and any ACLs setup.

[the1ts]

Just reading again, are you saying that you are proxying for example test.example.com to 192.168.0.166:7233 but 192.168.0.166:7233 is still available to hit?

[mouledla]

@the1ts Thats actually the problem which i am running into. Any suggestion or solution on how to fix this?

[the1ts]

As said before, the only thing I can think of is, on the host running docker, block all but the internal IP of the router from getting to the NPM port on the host. Can't be more specific since everyone's ports and IPs are different.

[github-actions]

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

[github-actions]

Issue was closed due to inactivity.