-
Notifications
You must be signed in to change notification settings - Fork 608
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Blank page : somethingWentWrongDescription #789
Comments
I have roughly the same setup as Sinaure's and experience the exact same bug, no issues on the logging side, keycloak started fine. I tried to run Keycloak 25.0.2 with the 2.4.4 version of the chart. Inspecting my browser console when accessing the administration UI, I have some blocked calls because of what seems like a protocol mixup -loading over HTTP rather than HTTPS- and denial by content security policy:
|
I am seeing the same issues as @ChristopheVilain during an attempt of KC 25.0.4 with chart version 2.5.0. |
actually there is already an issue for this and this comment helped me to get it running. i had the same problem. |
This issue has been marked as stale because it has been open for 30 days with no activity. It will be automatically closed in 10 days if no further activity occurs. |
deployed on a rancher cluster, extraEnv: |
++ I have forced the chart to use image tag 26.0.5, so far working flawless.... |
Blank page on : https://keycloak.mydomain.com/auth/admin/master/console/
upgrading from
2.3.0 -> 2.4.4
keycloak is running on port 8080
I have no error messages on startup:
2024-08-13 13:34:13,724 INFO [io.quarkus] (main) Keycloak 25.0.0 on JVM (powered by Quarkus 3.8.5) started in 18.705s. Listening on: http://0.0.0.0:8080. Management interface listening on http://0.0.0.0:9000.
The text was updated successfully, but these errors were encountered: