After updating to version 1.7.0 or 1.7.1, I also initially noticed the behaviour described in issue #1081. Some services work, but others do not. However, I have noticed something else that I am not sure is related to this or another issue.
Since updating Pangolin, there has been an issue with the X-Forwarded-For header in my Pocket-ID access log: only the internal Docker network IP is reported.
Originally created by @elcajon on GitHub (Jul 18, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/1084
After updating to version 1.7.0 or 1.7.1, I also initially noticed the behaviour described in issue #1081. Some services work, but others do not. However, I have noticed something else that I am not sure is related to this or another issue.
Since updating Pangolin, there has been an issue with the X-Forwarded-For header in my Pocket-ID access log: only the internal Docker network IP is reported.
<img width="1269" height="1106" alt="Image" src="https://github.com/user-attachments/assets/c4316a07-19c7-44d5-9e45-940bf97d5337" />
So I do have the issue reported in #1081 but I do not have your issue.
I do use pocket id but my IP is reported appropriately.
<!-- gh-comment-id:3089111645 -->
@R-Nabil commented on GitHub (Jul 18, 2025):
So I do have the issue reported in #1081 but I do not have your issue.
I do use pocket id but my IP is reported appropriately.
Is your client using IPv6 by any chance?
See #110 - this might be related to docker rather than the update.
<!-- gh-comment-id:3089123505 -->
@Xentrice commented on GitHub (Jul 18, 2025):
Is your client using IPv6 by any chance?
See #110 - this might be related to docker rather than the update.
Nice catch, thanks for that. I realized all the connections made today have been IPv6 instead of my home network which relies on IPv4. So I will close this. Thanks again.
<!-- gh-comment-id:3089334052 -->
@elcajon commented on GitHub (Jul 18, 2025):
> Is your client using IPv6 by any chance?
See https://github.com/fosrl/pangolin/issues/110 - this might be related to docker rather than the update.
Nice catch, thanks for that. I realized all the connections made today have been IPv6 instead of my home network which relies on IPv4. So I will close this. Thanks again.
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 @elcajon on GitHub (Jul 18, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/1084
After updating to version 1.7.0 or 1.7.1, I also initially noticed the behaviour described in issue #1081. Some services work, but others do not. However, I have noticed something else that I am not sure is related to this or another issue.
Since updating Pangolin, there has been an issue with the X-Forwarded-For header in my Pocket-ID access log: only the internal Docker network IP is reported.
@R-Nabil commented on GitHub (Jul 18, 2025):
So I do have the issue reported in #1081 but I do not have your issue.
I do use pocket id but my IP is reported appropriately.
@Xentrice commented on GitHub (Jul 18, 2025):
Is your client using IPv6 by any chance?
See #110 - this might be related to docker rather than the update.
@elcajon commented on GitHub (Jul 18, 2025):
Nice catch, thanks for that. I realized all the connections made today have been IPv6 instead of my home network which relies on IPv4. So I will close this. Thanks again.