Pangolin client connector shows wrong requesting IP #490

Closed
opened 2026-04-05 17:12:53 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @thutex on 12/13/2025

Describe the Bug

When adding a new user client (in my case, using the linux pangolin cli), you need to login and authorize this connection.
so far, so good.

however, the IP being displayed is not the one from the actual connection, but the one used to connect to the site, in my case, that of cloudflare.
i am assuming that this is related to the fact that badger also doesn't really handle cloudflare IPs correctly (as seen in another bug report)

but, since we are talking about a client here, which is running on a machine, it should be able to fetch the external IP of the connection for the machine it is running on, and provide that as the actual connecting IP, instead of (seemingly) relying on the IP given through the http connection towards the installation (as this might, for example, go through a proxy - such as in my case - and then showing the incorrect connecting IP for the client)

Environment

  • OS Type & Version: ubuntu
  • Pangolin Version: 1.13.0
  • Gerbil Version: n/a
  • Traefik Version: n/a
  • Newt Version: 1.7.0
  • Olm Version: n/a
  • Client Version: Pangolin CLI v0.1.1 (linux)

To Reproduce

simply make sure either your http connections are behind a proxy, or put your pangolin installation behind a proxy such as cloudflare.
then, connect a client.

the IP shown in the authorization window will be that of the proxy, not the external IP of the machine requesting the connection.

Expected Behavior

get the actual external IP through the client itself, instead of relying on the IP provided in the http connection that is established

*Originally created by @thutex on 12/13/2025* ### Describe the Bug When adding a new user client (in my case, using the linux pangolin cli), you need to login and authorize this connection. so far, so good. however, the IP being displayed is not the one from the actual connection, but the one used to connect to the site, in my case, that of cloudflare. i am assuming that this is related to the fact that badger also doesn't really handle cloudflare IPs correctly (as seen in another bug report) but, since we are talking about a client here, which is running on a machine, it should be able to fetch the external IP of the connection for the machine it is running on, and provide that as the actual connecting IP, instead of (seemingly) relying on the IP given through the http connection towards the installation (as this might, for example, go through a proxy - such as in my case - and then showing the incorrect connecting IP for the client) ### Environment - OS Type & Version: ubuntu - Pangolin Version: 1.13.0 - Gerbil Version: n/a - Traefik Version: n/a - Newt Version: 1.7.0 - Olm Version: n/a - Client Version: Pangolin CLI v0.1.1 (linux) ### To Reproduce simply make sure either your http connections are behind a proxy, or put your pangolin installation behind a proxy such as cloudflare. then, connect a client. the IP shown in the authorization window will be that of the proxy, not the external IP of the machine requesting the connection. ### Expected Behavior get the actual external IP through the client itself, instead of relying on the IP provided in the http connection that is established
MrUnknownDE added the non-critical bugnon-critical bug labels 2026-04-05 17:12:53 +02:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/pangolin#490