## TL;DR

Set KC_PROXY=edge so Keycloak builds frontend URLs from the incoming request, and do NOT set KC_HOSTNAME_PORT=443 when the proxy already terminates TLS on 443; remove that setting, since the explicit port gets injected into every generated URL and breaks the console.

## Steps

1. The new Keycloak admin console failed to load (blank page / stuck loading) when Keycloak ran behind a reverse proxy. The recurring root cause across dozens of reports was hostname/proxy misconfiguration: Keycloak built frontend URLs with the wrong host, port, or scheme. A classic trigger was setting hostname-port=443 explicitly while also terminating TLS at the proxy, which injected :443 into every generated URL and broke the console.

2. Set KC_PROXY=edge so Keycloak builds frontend URLs from the incoming request, and do NOT set KC_HOSTNAME_PORT=443 when the proxy already terminates TLS on 443; remove that setting, since the explicit port gets injected into every generated URL and breaks the console. Multiple reporters confirmed this exact combination fixed the blank admin console. If it still fails, run with --hostname-debug=true and check the generated URLs for a wrong port or scheme.

## When to use

You are seeing this: The new Keycloak admin console failed to load (blank page / stuck loading) when Keycloak ran behind a reverse proxy. Use this skill when you run into "Keycloak admin console not loading behind reverse proxy (hostname/proxy misconfiguration)".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

## Why this happens

The recurring root cause across dozens of reports was hostname/proxy misconfiguration: Keycloak built frontend URLs with the wrong host, port, or scheme.
