Clicking on the admin console link on the main page successfully redirects to the /admin/master/console/ path, but only displays a blank white page.
I have the server running in production mode on a custom Docker container based in Debian. I am not behind a proxy and I am using port 8443 with a self-signed SSL cert.
Same issue for me but running keycloak 17.01 & java jdk 18 in edge mode behind apache reverse proxy with external SSL and localhost:8080 hosted on win 2019 server VM. From either localhost or external https link keycloak initially loads start page but shows a blank page, not an error, when clicking on admin console - page appears to refresh every 10 seconds (blank webpage code below). Admin user previously created in dev mode. Same behaviour if I remove reverse proxy and apply ssl certs directly to keycloak. Also tried jdk 17 and using IIS as reverse proxy. Tested in multiple browsers. Can’t see any errors in logs but blank web page code below as it is serving some html.
Hi
I had a similar problem with keycloak 17.0.1 running on docker.
My Dockerfile was similar to the one suggested in the docker documentation, having:
ENV KC_HOSTNAME=localhost:8443
Using the browser debug tools i saw that every 10 seconds or so, keycloak was trying to get https://localhost:8443:8443. I changed to:
ENV KC_HOSTNAME=localhost
And it worked
Sadly that’s not my issue here, hostname is set to only localhost and page being called is localhost:8080. Aside from hostname, only other conf settings are for the postgres db.
Just FYI, I was having the same issue with keycloak 18 in production mode using the official image, I had to add the port to the KC_HOSTNAME variable too. That solved it for me
One can debug the issue relatively easy with F12 - debug console of the browser. One probably will see and request to something like https://127.0.0.1/something (given you are trying to bring it up on the local machine). There are 2 or 3 things to pay attention to: proper external hostname (including custom port) used to access keycloak from outside of the container and starting keycloak in dev mode. Dev mode will disable requirement for TLS (which you don’t have and need on local host). Here is my docker-compose.yaml, to start keycloak locally:
Hi,
I am facing the same issue while running keycloak:latest (19.0.1) docker container with external postgres database. Able to browse keycloak landing page on public_ip:8080 and recieving blank page for Adminstration Console URL: public_ip:8080/admin/master/console/
Accessing keycloak using VM’s public ip, host and docker port are mapped to 8080:8080
Using the Keycloak application manifest provided here example-kc.yamlBasic Keycloak deployment - Keycloak, I had to change hostname: test.keycloak.org
to hostname: localhost:8443.
No luck adding localhost:port, keycloak is taking the port from variable KC_HOSTNAME_PORT=8080
Getting this error message while loading step1.html file:
Request URL: http://localhost:8080/realms/master/protocol/openid-connect/3p-cookies/step1.html?version=f5656
Referrer Policy: no-referrer
Provisional headers are shown
Learn more
sec-ch-ua: “Chromium”;v=“106”, “Google Chrome”;v=“106”, “Not;A=Brand”;v=“99”
sec-ch-ua-mobile: ?0
sec-ch-ua-platform: “Windows”
Upgrade-Insecure-Requests: 1
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/106.0.0.0 Safari/537.36