Hi !
On the services deployed behind pangolin the user activity only shows private IP from newt tunnel.
There is some traefik plugins made for Cloudflare tunnels (which I do not use), that I tried without success. I don't find a lot of documentation on this subject, am I missing something ?
I am using pangolin 1.4.1 and the first version I deployed was the 1.1.0, if that helps :)
Example of activity on my jellyfin instance :
Originally created by @FirmYn on GitHub (May 27, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/788
Hi !
On the services deployed behind pangolin the user activity only shows private IP from newt tunnel.
There is some traefik plugins made for Cloudflare tunnels (which I do not use), that I tried without success. I don't find a lot of documentation on this subject, am I missing something ?
I am using pangolin 1.4.1 and the first version I deployed was the 1.1.0, if that helps :)
Example of activity on my jellyfin instance :
@oschwartz10612 commented on GitHub (May 27, 2025):
Hi! It depends on how your target service is extracting the client IP. The actual IP of the packets from Newt will always be its IP because it is a TCP reverse proxy, but there are headers added by Traefik to provide the real client IP. For example, see the below output of an http GET request through Pangolin to containous/whoami. The X-Forwarded-For and X-Real-Ip headers provide the real client IP.
<!-- gh-comment-id:2912719579 -->
@oschwartz10612 commented on GitHub (May 27, 2025):
Hi! It depends on how your target service is extracting the client IP. The actual IP of the packets from Newt will always be its IP because it is a TCP reverse proxy, but there are headers added by Traefik to provide the real client IP. For example, see the below output of an http GET request through Pangolin to `containous/whoami`. The `X-Forwarded-For` and `X-Real-Ip` headers provide the real client IP.
```
Hostname: 7fc073673a41
IP: 127.0.0.1
IP: ::1
IP: 172.17.0.3
RemoteAddr: 172.17.0.1:50730
GET / HTTP/1.1
Host: test.fosrl.io
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:131.0) Gecko/20100101 Firefox/131.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/png,image/svg+xml,*/*;q=0.8
Accept-Encoding: gzip, deflate, br, zstd
Accept-Language: en-US,en;q=0.5
Cookie: p_session_token_s.1748355702263=lr43yivmgqqqope53zgay7klzf6hyxos
Priority: u=0, i
Referer: https://p.fosrl.io/
Sec-Fetch-Dest: document
Sec-Fetch-Mode: navigate
Sec-Fetch-Site: same-site
Te: trailers
Upgrade-Insecure-Requests: 1
X-Forwarded-For: 100.36.185.88
X-Forwarded-Host: test.fosrl.io
X-Forwarded-Port: 443
X-Forwarded-Proto: https
X-Forwarded-Server: 5c039251d853
X-Real-Ip: 100.36.185.88
```
Thanks a lot, I was completely misunderstanding how it works !
sorry, for reviving this old issue, but did you solve this? Or you just learned to live with it?
<!-- gh-comment-id:2952911017 -->
@tuandatdavid commented on GitHub (Jun 7, 2025):
> Thanks a lot, I was completely misunderstanding how it works !
sorry, for reviving this old issue, but did you solve this? Or you just learned to live with it?
@oschwartz10612 commented on GitHub (Jun 8, 2025):
@tuandatdavid target application needs to be able to pull the IP out of the headers of the request. See above response.
This is usually mostly application specific and is hard to give a general answer for - sorry!
<!-- gh-comment-id:2954051399 -->
@oschwartz10612 commented on GitHub (Jun 8, 2025):
@tuandatdavid target application needs to be able to pull the IP out of the headers of the request. See above response.
This is usually mostly application specific and is hard to give a general answer for - sorry!
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @FirmYn on GitHub (May 27, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/788
Hi !
On the services deployed behind pangolin the user activity only shows private IP from newt tunnel.
There is some traefik plugins made for Cloudflare tunnels (which I do not use), that I tried without success. I don't find a lot of documentation on this subject, am I missing something ?
I am using pangolin 1.4.1 and the first version I deployed was the 1.1.0, if that helps :)
Example of activity on my jellyfin instance :
@oschwartz10612 commented on GitHub (May 27, 2025):
Hi! It depends on how your target service is extracting the client IP. The actual IP of the packets from Newt will always be its IP because it is a TCP reverse proxy, but there are headers added by Traefik to provide the real client IP. For example, see the below output of an http GET request through Pangolin to
containous/whoami. TheX-Forwarded-ForandX-Real-Ipheaders provide the real client IP.@FirmYn commented on GitHub (May 28, 2025):
Thanks a lot, I was completely misunderstanding how it works !
@tuandatdavid commented on GitHub (Jun 7, 2025):
sorry, for reviving this old issue, but did you solve this? Or you just learned to live with it?
@oschwartz10612 commented on GitHub (Jun 8, 2025):
@tuandatdavid target application needs to be able to pull the IP out of the headers of the request. See above response.
This is usually mostly application specific and is hard to give a general answer for - sorry!