Keycloak admin console isn't reachable
See original GitHub issueAfter deploying EnMasse with the Keycloak instance, the web console seems to be not reachable using the browser.
Getting the ip address of the standard-authservice
service and trying with following :
http://<ip-address>:8080/auth/admin/
I get this error :
This site can’t be reached
172.30.67.126 refused to connect.
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (6 by maintainers)
Top Results From Across the Web
Keycloak Admin console not accessible - Stack Overflow
I was able to fix it. The problem was that keycloak was redirecting the initial page from https://<my-domain>/ to https://<my-domain> ...
Read more >The option KC_HOSTNAME_ADMIN does not work
I want to set up access to the admin console only from a private interface (I had the same configuration in keycloak 16.x)....
Read more >Keycloak Account Management Console not working with ...
Login with wrong credentials to the admin console and look for the server logs -- they should contain an entry of the wrong...
Read more >Configuring the hostname - Server - Keycloak
To reduce attack surface, the administration endpoints for Keycloak and the Admin Console should not be publicly accessible. Therefore, you can secure them ......
Read more >keycloak admin console keep spinning with ip and not even ...
Clear the proxy setting. I actually had cloudflare create an origin cert and that fixed my issue.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The problem seems to be related to this error :
“protocol family unavailable”
which is related to the usage of the IPv6 stack. On my side even disabling IPv6 doesn’t fix the problem. The way to do that is set the preferred stack to use (IPv4) on Keycloak startup with this Java options :
java.net.preferIPv4Stack=true
So this issue is fixed by aa8cc3a603e379c2612328e2b4093b75a32f3723
this is because Jboss is listening only on 127.0.0.1
Solution is here: https://serverfault.com/questions/830053/cant-access-jboss-remotely-despite-of-proper-binding-of-ip-address-in-standalon