[BUG] keycloak blackscreen

Lissy93 / dashy

🚀 A self-hostable personal dashboard built for you. Includes status-checking, widgets, themes, icon packs, a UI editor and tons more!

https://dashy.to

MIT License

18.23k stars 1.38k forks source link

[BUG] keycloak blackscreen #341

Closed TheUdK closed 3 years ago

TheUdK commented 3 years ago

Environment

Self-Hosted (Docker)

Version

latest + tested 1.9.1 and 1.9.0

Describe the problem

Blackscreen after config build when keycloak enabled with all parameters.

Tried:

v1.9.0 / 1.9.1 / 1.9.2
locally hosted keycloak and dashy
k8s hosted keycloak and dashy
adding config params via yaml
adding config params via editor
keycloak valid redirect URIs and web origins with full URIs and also just wildcard

I am not getting any errors on the config build. All i get is just a black screen after the build and no log entries in either the keycloak or dashy containers that would point to any issues.

Additional info

No response

Please tick the boxes

[X] You are using a supported version of Dashy (check the first two digits of the version number)
[X] You've checked that this issue hasn't already been raised
[X] You've checked the docs and troubleshooting guide
[X] You agree to the code of conduct

liss-bot commented 3 years ago

Welcome to Dashy 👋 It's great to have you here, but unfortunately your ticket has been closed to prevent spam. Before reopening this issue, please ensure the following criteria are met.

Issues are sometimes closed when users:

Have only recently joined GitHub
Have not yet stared this repository
Have not previously interacted with the repo

Before you reopen this issue, please also ensure that:

You have checked that a similar issue does not already exist
You have checked the documentation for an existing solution
You have completed the relevant sections in the Issue template

Once you have verified the above standards are met, you may reopen this issue. Sorry for any inconvenience caused, I'm just a bot, and sometimes make mistakes 🤖

Lissy93 commented 3 years ago

Hiya, thanks for the question. I've not come across this issue before. Would you mind sharing the console output of your browser, (press F12) - there will probably be an error message, which will help me debug this. A redacted version of your config and any validation warnings (yarn validate-config) would also be helpful. Can you also confirm that your KC is setup with an user, realm and application?

If you could also share the browser's console output, that will likely show what the error is. If you've not yet set any redirect headers, then you'll probably see a CORS error there. This can be fixed by setting headers, following this guide.