eatoff Posted June 1, 2023 Share Posted June 1, 2023 (edited) I'm currently going through trying to put Nginx Proxy Manager (NPM) on a separate IP address from my hose machine. This will (hopefully) allow me to route some traffic internally. but, When i update the ports in the docker page for that container, they dont appear to be updating. Here is my Docker page: after startup: You can see after startup that the ports are still mapped for ports 4443 and 8080 instead of 443 and 80 The port forwarding on my router still works for using ports 4443 and 8080 instead of the new 443 and 80 ports i'm trying to map. Is there a trick to get this to update the mapping correctly? EDIT TO UPDATE: I switched to the official NPM template, and the ports are fine with that one. Edited June 1, 2023 by eatoff Quote Link to comment
Solution JonathanM Posted June 1, 2023 Solution Share Posted June 1, 2023 Port mapping only applies to bridge mode. When a container has a different IP address than the host, mapping is not used or needed, all ports are open and the listening port(s) are directly controlled by the application(s) in the container. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.