I faced an issue by configuring :
I tried to access the console with https://mydomain/keycloak and stay blocked on the spinning waiting page without any clue. Let's try to improve that :)
To gain time in configuration resolution
With a reverse proxy nginx and keycloak, login in admin console lead to be blocked on :
204 return code and no other errors.
I had to explore keycloak source code to find the cause ; this test failed in keycloak.js :
if ((event.origin !== loginIframe.iframeOrigin) in keycloak.js
After a (lot of) time of search, it appears that it compares :
because I'd setup
443 in keycloak.config
hostname-port make it works.
My keycloak configuration :
hostname=mydomain proxy=reencrypt hostname-strict=false #hostname-port=443 hostname-path=keycloak http-relative-path=keycloak hostname-admin-url=https://mydomain/keycloak
2 ways to improve it :
Thanks a lot for your analysis, it saved me (more) hours of research why KC wouldn't work with a reverse proxy anymore...
In addition to hostname-port being left empty, port 443 must also not be included in hostname-url.