hi @joerijansen ,
you may check the discussion here: [KC 17.0.1] with (httpd) reverse proxy does not consider X-Forwarded-For headers for resources in account-console · Issue #10997 · keycloak/keycloak · GitHub
Have you configured the quarkus.http.proxy.enable-forwarded-host=true in the conf/quarkus.properties file so that the x-forward headers are used?
is it possible that somehow your keycloak is reachable directly? (not going through the reverse proxy hostname)