NginxProxyManager / NginxProxyManager/nginx-proxy-manager
When i login to my DS file or any other Synology app, I get IP of the nginx container server instead of the login device
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 34.2k
- Forks
- 3.9k
- Avg merge
- 21h 12m
- Merged PRs (30d)
- 20
Description
@jc21
Hi,
I am aware that this issue has been mentioned to you in past, but I cannot crack it.
I running Docker compose NGINX 'jc21/nginx-proxy-manager:latest' image on my Synology NAS. I switched to this from the SWAG to renewing the certs all the time manually. But I have just notice, that every time I login the IP which gets reported, is the IP of the Docker NGINX container 192.168.96.2 instead of the IP of the device singing in, in the old SWAG setup I got the device real IP and when outside of WiFi reach, but the IP of the phone.
I have read majority of the posts, suggestions and fixes for the headers but none worked for me. Maybe I am not doing something right, I should also mention that I use Cloudflare.
Is there any reliable solution please? And if it is, can they be explained in detail what to, to get the correct device IP displayed instead of the container one?
I did tried these headers, one by one, and even together, no success.
set_real_ip_from ......./12;
set_real_ip_from ......./16;
real_ip_header X-Forwarded-For;
real_ip_recursive on;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
Thank you very much
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the login flow with the reported Docker Compose setup, including Cloudflare and Synology, then inspect which proxy hop supplies the client-IP headers. Compare the headers reaching the Synology app with those from the former SWAG setup. Done means the app consistently reports the signing device's real IP rather than 192.168.96.2.
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
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100