You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have deployed Keycloak using the Codecentric Helm charts versions 2.4.1, 2.4.2, and 2.4.3, but none of these versions are accessible. When attempting to access Keycloak via the Ingress URL, I'm encountering the following error in the browser console:
ERROR:
Mixed Content: The page at '' was loaded over HTTPS, but requested an insecure resource ''. This request has been blocked; the content must be served over HTTPS.
I'm unsure why this issue is occurring. I have attempted to resolve it by configuring the following environment variables in my Helm charts:
name: PROXY_ADDRESS_FORWARDING
value: "true"
name: KC_PROXY
value: "edge" # also tried "passthrough"
've searched for other solutions, but they don't seem to apply to this version of Keycloak. Any assistance with resolving this issue would be greatly appreciated. Thank you!
The text was updated successfully, but these errors were encountered:
I have deployed Keycloak using the Codecentric Helm charts versions 2.4.1, 2.4.2, and 2.4.3, but none of these versions are accessible. When attempting to access Keycloak via the Ingress URL, I'm encountering the following error in the browser console:
ERROR:
Mixed Content: The page at '' was loaded over HTTPS, but requested an insecure resource ''. This request has been blocked; the content must be served over HTTPS.
I'm unsure why this issue is occurring. I have attempted to resolve it by configuring the following environment variables in my Helm charts:
value: "true"
value: "edge" # also tried "passthrough"
My startup commands are configured as:
command:
and the environment variables are set as
extraEnv: |
value: admin
value: admin
value: >-
-Djgroups.dns.query={{ include "keycloak.fullname" . }}-headless
-Dkeycloak.hostname=myhostname
-Dkeycloak.proxy=forward
value: "true"
value: "edge"
've searched for other solutions, but they don't seem to apply to this version of Keycloak. Any assistance with resolving this issue would be greatly appreciated. Thank you!
The text was updated successfully, but these errors were encountered: