mirror of
https://github.com/fosrl/pangolin.git
synced 2026-07-19 08:05:10 -05:00
[GH-ISSUE #1311] [BUG] 502 error on apps on local/same host #35269
Reference in New Issue
Block a user
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 @dev-Blaze on GitHub (Aug 21, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/1311
It seems like any apps/services hosted on the same host as pangolin reverse proxy (Racknerd VPS) have trouble authenticating via OIDC (pocket-id) which the auth provider is also behind Pangolin and also on the same host.
whats weird is that services on a remote/newt site work fine, authentication works no issues. only issues with services that are local.
Services not using pocket-id for auth (login form/basic auth) work fine as well.
NOTE: i am not using pocket-id for pangolin authentication itself, this is auth for the separate applications with oidc functionality. pangolin is strictly just the reverse proxy in this scenario.
all services are docker containers, and I have also verified that the individual containers can ping the pangolin container, they are all on the same docker network.
pangolin version 1.8.0
gerbil 1.1.0
traefik 3.5.0
Example - outline app using pocketid for oidc auth.
Logs from Pocket ID:
Log from Outline Application:
Any help would be appreciated. Thanks
@oschwartz10612 commented on GitHub (Aug 31, 2025):
Hi sorry for the delay!
Do you get bad gateway after going through pocket id or before? Do you
get the bad gateway when you are sent to pocket id? I agree this does
not make any sense.
A gut reaction is that it would be because pangolin cant reach those
local containers but if you say it works without oidc this does not make
sense.
Can you try updating to the latest version and see if that helps at all.
Remember to backup config/ first.
@github-actions[bot] commented on GitHub (Sep 15, 2025):
This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
@github-actions[bot] commented on GitHub (Sep 30, 2025):
This issue has been automatically closed due to inactivity. If you believe this is still relevant, please open a new issue with up-to-date information.