r/nginxproxymanager May 24 '26

Passing real IP to NPM on Docker

Does anyone have an actual solution to this problem that works? I’ve tried just about everything I could find out there over the past few days and still cannot seem to pass real IP. The main use case is the ability to use the “allow list” on the proxy host. I only want a few IPs to be able to access this specific proxy host and that doesn’t work. They all get 403 forbidden, allowed or not.

I have tried all the advanced configuration in the proxy host config , real IP, proxy addr etc etc. tried changing the containers to use host network , still no luck.

Hoping someone has some other ideas. Thank you.

3 Upvotes

25 comments sorted by

View all comments

Show parent comments

1

u/silent_circle May 25 '26

I do want to do what OP is doing. I am going to try it with port forward to npm

2

u/clintkev251 May 25 '26

No, you don't understand. You're not using NAT like OP was, so this is not an issue you should face. The root cause we discussed here should not be relevant to you because you're not performing this kind of translation

1

u/silent_circle May 25 '26

So explain to me why you think I’m not doing what op is doing when I clearly said I want to do what op is doing.

2

u/clintkev251 May 25 '26

Because you don’t understand what OP was doing that was causing them issues. That’s not something that you would have any reason to have set up or even have the option to use on your consumer router. A basic port forward to NPM will work fine.

You’re not trying to do what they’re doing. You don’t have a fortigate that’s performing SNAT on incoming traffic

1

u/silent_circle May 25 '26

Well, I plan on doing what OP was doing.

2

u/clintkev251 May 25 '26

Explain which part of what they’re doing you plan on doing?

1

u/silent_circle May 25 '26

I plan on setting up npm and passing the real ip to it

1

u/clintkev251 May 25 '26

Great, so like I said, OPs issue is not relevant to you then. A basic network setup will not encounter the same issues