Repository navigation
Before reporting an issue
Areaadmin/ui Describe the bugWhenever I have booted up keycloak using My setup: The docker compose configuration I'm using: If I open up the hostname-debug page from within my network it looks like the image below. If I open it up using my phone (not connected to the home network) it says Frontend, Backend and Admin OK... What am I doing wrong? Version26.3.1 Regression
Expected behaviorKeycloak to be usable from within and from outside my home network Actual behaviorKeycloak isn't usable from within my home network How to Reproduce?
Anything else?No response |
Replies: 1 comment 4 replies
|
Note that KC_PROXY_ADDRESS_FORWARDING is not a keycloak option, and KC_HOSTNAME_STRICT does not have an effect if a hostname is set (you should see that in the startup log). The configured hostname for keycloak is assumed to be public. If you are accessing a front end or admin url, it will need to be via that. With KC_HOSTNAME_BACKCHANNEL_DYNAMIC you will be able to access backchannel urls dynamically from behind the proxy. In your case it simply sounds like keycloak.some.domain is not really a public url and is not resolvable in your home network. You will likely need to add a hosts entry. Note also that KC_PROXY_ADDRESS_FORWARDING is not a keycloak option. |
When you perform an nslookup from a machine on your home network, does it resolve to the expected proxy server? If it does, and you are hitting the hostname debug page via request via that proxy server, then it's not an issue…