mirror of
https://github.com/pocket-id/pocket-id.git
synced 2025-12-06 09:13:19 +03:00
🐛 Bug Report: Getting 502 Error on all clients after 1.7.0 update #87
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.
Reproduction steps
As the title states, I tried reverting back to 1.6.4 but it doesn't seem to be allowed.
Currently hosting Pocket ID via docker
Pocket ID and all of the services are behind Reverse Proxy Pangolin (Uses Traefik)
Logs from Pocket ID:
Log from Outline Application:
Expected behavior
Authentication working
Actual Behavior
Getting 502 Server Error
Version and Environment
v1.7.0
Log Output
Previous notes
@ghoshsaptarshi commented on GitHub:
I was facing the same error. If you're using docker then try changing the variable name from
PUBLIC_APP_URLtoAPP_URL.The
https://<your-pocket-id-domain>/.well-known/openid-configurationwas pointing to localhost instead of the correct domain.@stonith404 commented on GitHub:
@dev-Blaze Is Pocket ID accessible from the other containers? You can test this by running
ping your-pocket-id-domaininside the containers that can't authenticate. I doubt that the issue is caused by the update, because we shouldn't have changed anything that could cause the issue.@stonith404 commented on GitHub:
Can you share the output of
https://<your-pocket-id-domain>/.well-known/openid-configuration?Besides logging into clients everything works as expected?
@dev-Blaze commented on GitHub:
@stonith404 it does seem to be accessible from other containers.
@dev-Blaze commented on GitHub:
one thing I have noticed is that, in pangolin, it has tunnels to other hosts to reverse proxy services/apps in different local networks as well.
this issue only happens for services that are local that are on the pangolin host itself and doesnt happen for services that are proxies with its tunnel on a different host.
this might point to the issue being with the reverse proxy but this only started after the update to Pocket-ID
@kmendell commented on GitHub:
Did you make a configuration changes to your reverse proxy setup? Like @stonith404 nothing in the 1.7.0 update should have effected this, and from my overview it seems like a configuration issue but I could be wrong too. It may be helpful to share you docker compose, and .env redacting any sensitive data where needed.
@dev-Blaze commented on GitHub:
pocket-id is behind the same reverse proxy and I can log into it without issues, its just other services using pocket-id as oauth provider having issues. I'll paste the docker compose and env file here in a bit
@dev-Blaze commented on GitHub:
@ghoshsaptarshi I am using the APP_URL and not PUBLIC_APP_URL for the pocket-if docker-compose stack.
@dev-Blaze commented on GitHub:
docker-compose file
stack.env
@dev-Blaze commented on GitHub:
@kmendell I have not made any changes to the reverse proxy config either.
@stonith404 commented on GitHub:
Would you mind setting up a test instance on v1.6.4 and try it again? I'm really confident that the issue is not caused by v1.7.0.
@dev-Blaze commented on GitHub:
I tested with a test instance on v1.6.4 and it does look to have the same problem. I'll post in the pangolin page. Thanks gents
@stonith404 commented on GitHub:
Alright, thanks for testing. Good luck!