Loading the admin console... not happening

Configuring the server
1

Hi,

I used to run keycloak, and it was fetching the 17.0.0 version. But then when we changed to the 19 version, I had to adapt a lot of things to make it work. Finally, everything seems to be working, except that I don’t get the admin console.

I always the the page “Loading the admin console” with a spinning circle.

I have googled it non stop, but have no idea how to fix this. Access to realms seem to work, but I don’t know why the admin console doesn’t load.

Here’s my deployment configuration:

apiVersion: apps/v1
kind: Deployment
metadata:
  name: keycloak
  namespace: side-prod
  labels:
    app: keycloak
    service: keycloak
spec:
  replicas: 1
  selector:
    matchLabels:
      app: keycloak
      service: keycloak
  template:
    metadata:
      labels:
        app: keycloak
        service: keycloak
    spec:
      containers:
      - name: keycloak
        image: quay.io/keycloak/keycloak:latest
        args: ["start"]
        ports:
        - name: http
          containerPort: 8080
        env:
        - name: KC_HOSTNAME_STRICT_HTTPS
          value: "false"
        - name: KC_HOSTNAME_STRICT
          value: "false"
        - name: KC_TRANSACTION_XA_ENABLED
          value: "false"
        - name: KC_HTTP_ENABLED
          value: "true"
        - name: KC_HTTP_RELATIVE_PATH
          value: "auth"
        - name: KEYCLOAK_USER
          value: "admin"
        - name: KEYCLOAK_PASSWORD
          value: "SOMEPASS"
        - name: KEYCLOAK_FRONTEND_URL
          value: "https://prod.mydomain.com/auth"
        - name: KC_HOSTNAME
          value: "prod.mydomain.com"
        - name: KC_PROXY
          value: "none"
        - name: KC_PROXY_ADDRESS_FORWARDING
          value: "true"
        - name: KC_DB
          value: "postgres"
        - name: KC_DB_URL
          value: "jdbc:postgresql://10.11.11.10/keycloak"
        - name: KC_DB_USERNAME
          value: "keycloak"
        - name: DB_SCHEMA
          value: "public"
        - name: KC_DB_PASSWORD
          value: "REDACTED"
        - name: KEYCLOAK_LOGLEVEL
          value: "DEBUG"
        - name: WILDFLY_LOGLEVEL
          value: "DEBUG"
        # readinessProbe:
          # httpGet:
            # path: /auth/realms/master
            # port: 8080

I have tried to change the proxy to passthrough and to edge, to no avail.

My ingress is configured like this:

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
    name: keycloak-ingress
    namespace: side-prod
    labels:
        app: keycloak
        service: keycloak
spec:
    ingressClassName: nginx
    rules:
    - host: prod.mydomain.com
      http:
        paths:
          - path: /auth
            pathType: Prefix
            backend:
              service:
                name: keycloak
                port:
                  number: 8080

Could anyone give me a hint on how to fix this?

Best,

Francis

2

Try ["start", "--proxy=edge"]

1 Like
3

Thanks, @weltonrodrigo, but it didn’t work.

4

I found the issue - I think. I am running Kubernetes with metallb, which does not preserve (without many changes to my setup) the IP address of the origin. I was using an nginx-ingress to get to it, but apparently it wasn’t happy.
I installed it on a docker container outside the cluster, and everything works fine.

1 Like
5

Thanks weltonrodrigo that worked for me as I was having a similar issue.

Pat