Skip to content

Is the docker network the best practice? Why would one want double NAT? How to change default ports #5010

@atais

Description

@atais

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

Why is https://nginxproxymanager.com/advanced-config/#best-practice-use-a-docker-network considered "best practce"?

I am using now the docker network to connect all my internal services on a NAS, but actually this setup makes my life much harder because of docker networks NAT.

  1. My internal network is 192.168.100.0/24
  2. Docker internal netowrk is 172.29.16.0/24
  3. I can't use access list rules, because all the IPs are being translated to the docker IP
  4. I don't see correct IPs on audit log in my apps
  5. but the benefit is that its easier to connect the services :D

I am no network master but I have technical background. I have consulted chatgpt and the docker's network is essentially a double NAT and its "expected behaviour" but i would consider this as a major downside of this "best practice".

On the other hand, I can't run network_mode: host because the ports 80, 81, 443 are occupied on my system.
So it would be extremely useful to me if I could change the default ports by using ENV values

Nginx Proxy Manager Version

2.13.5

Expected behavior

  • I'd like to see the original IP in my logs
  • Access List rules IPs should work
  • change default ports with ENV values

Operating System

QNAP nas

NAT References:

Port References:

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions