mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-28 10:55:54 +03:00
[GH-ISSUE #2573] Can't show the Client real ip #1793
Labels
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#1793
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @g-marinov on GitHub (Jan 31, 2023).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2573
jc21/nginx-proxy-manager:latestdocker image?Describe the bug
No matter what I did can't see the client real IP, I can see only the docker IP.
LOGS:
web-address is the webpage I'm accessing
Nginx Proxy Manager Version
jc21/nginx-proxy-manager:latest
Operating System
Docker Desktop
Additional context
FastApi
@navhawk80 commented on GitHub (Jan 31, 2023):
Please del
@g-marinov commented on GitHub (Feb 2, 2023):
Hi navhawk80, this doesn't fix the problem.
After a few hours of tests, I finally find the problem. The problem is the Windows 🥇, it's not only nginx, traefik has the same issue ... When I switch to my ubuntu server everything was working well.
@navhawk80 commented on GitHub (Feb 2, 2023):
Hi,
Please disregard info I mentioned above.
Real fix was the script from here https://gist.github.com/pedrolamas/db809a2b9112166da4a2dbf8e3a72ae9
I put it into startup on my synology and now in LOGs external IPs are beaing reconnized correctly.
@github-actions[bot] commented on GitHub (Jan 29, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (Mar 15, 2025):
Issue was closed due to inactivity.