search

leonardochappuis / keycloak-docker

5 stars 9 forks source link

INFO: Can't log in to the admin console - iframe fails to load with 403 #2

Open pawelkrystkiewicz opened 2 weeks ago

pawelkrystkiewicz commented 2 weeks ago

After deployment today, I had issue entering the admin console of keycloak. After some research, I figured out that config was missing KC_HOSTNAME_ADMIN_URL because after adding it, I could finally enter the login page.

I guess KC_HOSTNAME_ADMIN will also suffice.

If this is not a bug, it would be helpful to add some info about this behaviour to the README of this template

davidbattalion commented 2 weeks ago

After deployment today, I had issue entering the admin console of keycloak. After some research, I figured out that config was missing KC_HOSTNAME_ADMIN_URL because after adding it, I could finally enter the login page.

Also facing this issue.. What did you set the KC_HOSTNAME_ADMIN_URL variable to? Just ${{RAILWAY_PUBLIC_DOMAIN}} ?

pawelkrystkiewicz commented 2 weeks ago

After deployment today, I had issue entering the admin console of keycloak. After some research, I figured out that config was missing KC_HOSTNAME_ADMIN_URL because after adding it, I could finally enter the login page.

Also facing this issue.. What did you set the KC_HOSTNAME_ADMIN_URL variable to? Just ${{RAILWAY_PUBLIC_DOMAIN}} ?

@davidbattalion I got:

KC_HOSTNAME_URL=https://${{RAILWAY_PUBLIC_DOMAIN}}
KC_HOSTNAME_ADMIN_URL=https://${{RAILWAY_PUBLIC_DOMAIN}}

From what I understand from the docs, if you want to set ...HOSTNAME alone, then skip the protocol (https) and leave variable only.

Also, you can't have both ...HOSTNAME and ...HOSTNAME_URL so just pick one. I picked the ...URL

#this will cause error during deployment
KC_HOSTNAME_URL=https://${{RAILWAY_PUBLIC_DOMAIN}}
KC_HOSTNAME=${{RAILWAY_PUBLIC_DOMAIN}}