Repository navigation
Replies: 1 comment 1 reply
To clarify with http disabled you are running in reencrypt, not edge mode.
The hostname should reflect how keycloak is externally accessed via the proxy, which appears to be keycloak.internal.nsb-software.de |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hi everyone,
I’m having trouble setting up Keycloak behind an Nginx reverse proxy. Everything seems to be working — SSL handshake is successful, Nginx correctly forwards to Keycloak, and I get 302 redirects — but when I open the site in a browser, I only see a blank page.
Here’s all the relevant information about my setup:
Environment
I can:
ping keycloak.internal.abc.de successfully
Access Keycloak directly with curl:
curl -vk https://keycloak.internal.abc.deSo Keycloak is HTTPS only, no HTTP listener enabled, and it’s in edge proxy mode.
Here’s my current Nginx config for Keycloak:
What works:
Curl to Nginx endpoint returns 302 redirect to /admin/
Keycloak logs show successful startup, no errors
What doesn’t work:
When I open https://keycloak.internal.abc.de in a browser, I just get a blank white page.
Browser network tab shows requests going out, but the page doesn’t load correctly.
What I’ve already tried:
Confirmed Nginx can connect to Keycloak directly
→ Works, returns 302.
Any help or suggestions would be appreciated
All reactions