mirror of
https://github.com/yusing/godoxy.git
synced 2026-01-11 22:30:47 +01:00
Global OIDC triggering auth rate limit error with pocket ID #126
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 @Strontium on GitHub (Dec 20, 2025).
When using the global OIDC configuration with pocket-id i'm getting a "auth rate limit exceeded" error when navigating to the godoxy webui or other proxied apps.
Works as expected with godoxy v0.20.7
I've tried a fresh build keeping as close to supplied example configuration as I could and still faced the same issue. Any help would be appreciated.
config.yml
godoxy-compose.yml
.env
pocket-id-compose.yml
@yusing commented on GitHub (Dec 20, 2025):
I have tried to reproduce with the similar config. Things worked fine for me.
Is v0.20.7 the last version that works for you?
@Strontium commented on GitHub (Dec 20, 2025):
Correct. It's working fine with v0.20.7, upgrade to v0.20.8 or latest and it throws the error.
@yusing commented on GitHub (Dec 22, 2025):
Made some fixes, please try
ghcr.io/yusing/godoxy:nightly.@Strontium commented on GitHub (Dec 22, 2025):
Still the same issue, with a differently formatted auth rate limit error. Clicking try again redirects back to pocket id, which is signed in ok. It's just the protected apps that give this error. Interestingly I get the same error if I bypass the godoxy global OIDC auth for an app and use the apps built-in OIDC integrated logon method.
@yusing commented on GitHub (Dec 22, 2025):
could you turn
GODOXY_DEBUG=1in.env. reproduce the issue, and find logs like these?@Strontium commented on GitHub (Dec 22, 2025):
Here are the debug logs:
(it's a temp test instance so if I left something secure in the logs it should be fine)
@yusing commented on GitHub (Dec 22, 2025):
Pushed another fix to
nightly, please update and try again.@Strontium commented on GitHub (Dec 22, 2025):
Nailed it. It's all working as far as I can tell. Amazing work!! 🥇
@yusing commented on GitHub (Dec 22, 2025):
Great. Remember to switch back to
lateston next release!