Menu

1 / 5

Keycloak Behind a Reverse Proxy: Fix HTTPS Required

DEV Community: docker·DeployLark·10 days ago
#zU9fgM1s
#devtodocker#devto#dev#keycloak#example
Reading 0:00
15s threshold

You open Keycloak in the browser and get a grey page that says We are sorry... HTTPS required . Or you put it behind nginx, and the admin console stays blank, or the login page says Invalid parameter: redirect_uri . Your app then rejects every token with Invalid token issuer . All of these come from the same question: what URL does Keycloak think it lives at?

This guide reproduces each error with quay.io/keycloak/keycloak:26.8.1 , nginx:1.31.8 and postgres:18.6 in Docker Compose and fixes it. Every error message below comes from that lab run on November 4, 2026. The lab used the name auth.example.test with a self-signed certificate in place of your real domain.

These errors are common. On Stack Overflow, keycloak Invalid parameter: redirect_uri had 505,136 views on November 4, 2026, and "HTTPS required" while logging in to Keycloak as admin had 136,879.

The short version:

HTTPS required means a client with a public IP address reached Keycloak over plain HTTP. Put a TLS proxy in front.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.