mirror of
https://github.com/plankanban/planka.git
synced 2026-02-24 19:08:59 +03:00
OIDC failed to load #456
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 @chrellrich on GitHub (Apr 1, 2024).
Hi, i am not sure if im just missing something or wether there actually is an issue here.
I am using planka with Keycloak as my IDP.
Docker compose file:
In Keycloak I created a Client called planka with Client Authentication enabled and copied the client secret into my compose file.
When I start the container I get the following error.
Is there any other place where logs are written to? I haven't had the chance to test with a diffrent IDP yet, but i did verify that https://auth.my-domain.com/realms/master/.well-known/openid-configuration is accessible from within the container. I also tried some older releases but 1.15.5 and 1.15.0 gave the same error.
Any help in figuring this out is very much appreciated.
@mostdcoa commented on GitHub (Apr 1, 2024):
@chrellrich FWIW, I've had a similar issue and it was because I misconfigured my docker network. I would ensure that you're Planka container can communicate with your Keycloak container.
@chrellrich commented on GitHub (Apr 5, 2024):
Thanks for the response. They can communicate, i tested using wget. But it might be an issue when using multiple docker networks. I will try with a diffrent networks setup and report back for anyone else having similar problems.
@marttasch commented on GitHub (Apr 16, 2024):
I have basically the same docker compose setup, but using Authentik as IDP.
Worked flawlessly, until i restarted the Host machine. Since then i get the same error. Planka can ping Authentik and can use wget to get oidc-config from Authentik. I tried changing the docker network setup, with no luck.
Edit: No Idea what I did, change things back and force. Now its working with the same settings as before.
@zloveless commented on GitHub (Jun 14, 2024):
I just noticed this happen in my setup and the VM running my idp was locked up (cause undetermined atm). Rebooted it and everything came back online.