NginxProxyManager / NginxProxyManager/nginx-proxy-manager

NPM and webmin

Open
#3,431 13 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

stale
Dominant language
TypeScript
Stars
34.2k
Forks
3.9k
Avg merge
21h 12m
Merged PRs (30d)
20

Description

Hi

I am running Webmin behind NPM. The problem i am having is that when i am visiting Webmin admin portal i get the same loggin ip as the NPM docker contatiner host. In this case 192.168.1.118 when the ip should be 192.168.1.160.

Any suggesting when it comes to get webmin to understand my true IP address?

I have sett the following headers in NPM advance section:

real_ip_header CF-Connecting-IP;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

And in Webmin i have turn the following setting on: Trust remote IP address provided by proxies.

Can i somehow add another proxy_set_header ??

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Nginx Proxy Manager advanced proxy headers and Webmin's “Trust remote IP address provided by proxies” setting described in the issue. Reproduce the proxied request and verify which forwarded address Webmin records; done means the Webmin admin portal logs 192.168.1.160 instead of the NPM container host address.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, nginx
Domain
networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.