Keycloak 17.0.0 results in "page not found" for admin url

jeffreyporter · February 17, 2022, 1:04pm

I have tried the following Docker image and the download zip of version 17.0.0 and I get the same results

On using the URL http://localhost:8080/auth/admin I get a “page not found” message.
Note: this is not https

Here is the log file when the error occurs…

2022-02-17 12:57:52,619 DEBUG [org.keycloak.transaction.JtaTransactionWrapper] (executor-thread-3) new JtaTransactionWrapper
2022-02-17 12:57:52,619 DEBUG [org.keycloak.transaction.JtaTransactionWrapper] (executor-thread-3) was existing? false
2022-02-17 12:57:52,620 DEBUG [org.keycloak.services.error.KeycloakErrorHandler] (executor-thread-3) Error response 404: javax.ws.rs.NotFoundException: RESTEASY003210: Could not find resource for full path: http://localhost:8080/auth/admin
	at org.jboss.resteasy.core.registry.SegmentNode.match(SegmentNode.java:152)
	at org.jboss.resteasy.core.registry.RootNode.match(RootNode.java:74)
	at org.jboss.resteasy.core.registry.RootClassNode.match(RootClassNode.java:47)
	at org.jboss.resteasy.core.ResourceMethodRegistry.getResourceInvoker(ResourceMethodRegistry.java:480)
	at org.jboss.resteasy.core.SynchronousDispatcher.getInvoker(SynchronousDispatcher.java:332)
	at org.jboss.resteasy.core.SynchronousDispatcher.lambda$invoke$4(SynchronousDispatcher.java:253)
	at org.jboss.resteasy.core.SynchronousDispatcher.lambda$preprocess$0(SynchronousDispatcher.java:161)
	at org.jboss.resteasy.core.interception.jaxrs.PreMatchContainerRequestContext.filter(PreMatchContainerRequestContext.java:364)
	at org.jboss.resteasy.core.SynchronousDispatcher.preprocess(SynchronousDispatcher.java:164)
	at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:247)
	at io.quarkus.resteasy.runtime.standalone.RequestDispatcher.service(RequestDispatcher.java:73)
	at io.quarkus.resteasy.runtime.standalone.VertxRequestHandler.dispatch(VertxRequestHandler.java:151)
	at io.quarkus.resteasy.runtime.standalone.VertxRequestHandler.handle(VertxRequestHandler.java:82)
	at io.quarkus.resteasy.runtime.standalone.VertxRequestHandler.handle(VertxRequestHandler.java:42)
	at io.vertx.ext.web.impl.RouteState.handleContext(RouteState.java:1212)
	at io.vertx.ext.web.impl.RoutingContextImplBase.iterateNext(RoutingContextImplBase.java:163)
	at io.vertx.ext.web.impl.RoutingContextImpl.next(RoutingContextImpl.java:141)
	at io.quarkus.vertx.http.runtime.StaticResourcesRecorder$2.handle(StaticResourcesRecorder.java:67)
	at io.quarkus.vertx.http.runtime.StaticResourcesRecorder$2.handle(StaticResourcesRecorder.java:55)
	at io.vertx.ext.web.impl.RouteState.handleContext(RouteState.java:1212)
	at io.vertx.ext.web.impl.RoutingContextImplBase.iterateNext(RoutingContextImplBase.java:163)
	at io.vertx.ext.web.impl.RoutingContextImpl.next(RoutingContextImpl.java:141)
	at io.quarkus.vertx.http.runtime.VertxHttpRecorder$5.handle(VertxHttpRecorder.java:362)
	at io.quarkus.vertx.http.runtime.VertxHttpRecorder$5.handle(VertxHttpRecorder.java:340)
	at io.vertx.ext.web.impl.RouteState.handleContext(RouteState.java:1212)
	at io.vertx.ext.web.impl.RoutingContextImplBase.iterateNext(RoutingContextImplBase.java:163)
	at io.vertx.ext.web.impl.RoutingContextImpl.next(RoutingContextImpl.java:141)
	at org.keycloak.quarkus.runtime.integration.web.QuarkusRequestFilter.lambda$createBlockingHandler$1(QuarkusRequestFilter.java:66)
	at io.vertx.core.impl.ContextImpl.lambda$null$0(ContextImpl.java:159)
	at io.vertx.core.impl.AbstractContext.dispatch(AbstractContext.java:100)
	at io.vertx.core.impl.ContextImpl.lambda$executeBlocking$1(ContextImpl.java:157)
	at io.quarkus.vertx.core.runtime.VertxCoreRecorder$13.runWith(VertxCoreRecorder.java:543)
	at org.jboss.threads.EnhancedQueueExecutor$Task.run(EnhancedQueueExecutor.java:2449)
	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1478)
	at org.jboss.threads.DelegatingRunnable.run(DelegatingRunnable.java:29)
	at org.jboss.threads.ThreadLocalResettingRunnable.run(ThreadLocalResettingRunnable.java:29)
	at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
	at java.base/java.lang.Thread.run(Thread.java:829)

2022-02-17 12:57:52,625 DEBUG [freemarker.cache] (executor-thread-3) Couldn't find template in cache for "error.ftl"("en_GB", UTF-8, parsed); will try to load it.
2022-02-17 12:57:52,625 DEBUG [freemarker.cache] (executor-thread-3) TemplateLoader.findTemplateSource("error_en_GB.ftl"): Not found

I have started the service via this command…

./kc.sh start-dev --log-level=DEBUG

Version: keycloak-17.0.0.zip

Any ideas on how to resolve this?

Thanks
Jeff

I have just found the following bug raised:

github.com/keycloak/keycloak

Keycloak 17 docker admin console 404 not found

opened 03:55AM - 17 Feb 22 UTC

manbobo2002

kind/bug area/dist/quarkus status/triage

### Describe the bug Keycloak 17 admin console shows 404 error ``` keyclo…ak.js?version=lpr7f:1956 GET https://[domain]/realms/master/protocol/openid-connect/3p-cookies/step1.html?version=lpr7f 404 ``` Even curl in the container still has the same issue ``` bash-4.4$ curl https://[domain]/realms/master/protocol/openid-connect/3p-cookies/step1.html?version=lpr7f <html> <head><title>404 Not Found</title></head> <body bgcolor="white"> <center><h1>404 Not Found</h1></center> <hr><center>nginx</center> </body> </html> ``` ### Version 17.0.0 ### Expected behavior _No response_ ### Actual behavior ``` $ docker logs keycloak Changes detected in configuration. Updating the server image. Updating the configuration and installing your custom providers, if any. Please wait. 2022-02-17 03:24:10,702 INFO [io.quarkus.deployment.QuarkusAugmentor] (main) Quarkus augmentation completed in 6149ms Server configuration updated and persisted. Run the following command to review the configuration: kc.sh show-config Next time you run the server, just run: kc.sh start --spi-connections-jpa-default-migration-strategy=update 2022-02-17 03:24:13,217 INFO [org.keycloak.quarkus.runtime.hostname.DefaultHostnameProvider] (main) Hostname settings: FrontEnd: <domain>, Strict HTTPS: true, Path: <request>, Strict BackChannel: false, Admin: <request> 2022-02-17 03:24:13,987 WARN [org.infinispan.CONFIG] (keycloak-cache-init) ISPN000569: Unable to persist Infinispan internal caches as no global state enabled 2022-02-17 03:24:14,003 WARN [org.infinispan.PERSISTENCE] (keycloak-cache-init) ISPN000554: jboss-marshalling is deprecated and planned for removal 2022-02-17 03:24:14,052 INFO [org.infinispan.CONTAINER] (keycloak-cache-init) ISPN000556: Starting user marshaller 'org.infinispan.jboss.marshalling.core.JBossUserMarshaller' 2022-02-17 03:24:14,271 INFO [org.infinispan.CONTAINER] (keycloak-cache-init) ISPN000128: Infinispan version: Infinispan 'Triskaidekaphobia' 13.0.5.Final 2022-02-17 03:24:14,367 INFO [org.infinispan.CLUSTER] (keycloak-cache-init) ISPN000078: Starting JGroups channel `ISPN` 2022-02-17 03:24:14,368 INFO [org.infinispan.CLUSTER] (keycloak-cache-init) ISPN000088: Unable to use any JGroups configuration mechanisms provided in properties {}. Using default JGroups configuration! 2022-02-17 03:24:14,436 WARN [org.jgroups.protocols.UDP] (keycloak-cache-init) JGRP000015: the send buffer of socket MulticastSocket was set to 1.00MB, but the OS only allocated 212.99KB 2022-02-17 03:24:14,437 WARN [org.jgroups.protocols.UDP] (keycloak-cache-init) JGRP000015: the receive buffer of socket MulticastSocket was set to 20.00MB, but the OS only allocated 212.99KB 2022-02-17 03:24:14,437 WARN [org.jgroups.protocols.UDP] (keycloak-cache-init) JGRP000015: the send buffer of socket MulticastSocket was set to 1.00MB, but the OS only allocated 212.99KB 2022-02-17 03:24:14,437 WARN [org.jgroups.protocols.UDP] (keycloak-cache-init) JGRP000015: the receive buffer of socket MulticastSocket was set to 25.00MB, but the OS only allocated 212.99KB 2022-02-17 03:24:16,448 INFO [org.jgroups.protocols.pbcast.GMS] (keycloak-cache-init) 3ad955a78ecb-42249: no members discovered after 2004 ms: creating cluster as coordinator 2022-02-17 03:24:16,461 INFO [org.infinispan.CLUSTER] (keycloak-cache-init) ISPN000094: Received new cluster view for channel ISPN: [3ad955a78ecb-42249|0] (1) [3ad955a78ecb-42249] 2022-02-17 03:24:16,465 INFO [org.infinispan.CLUSTER] (keycloak-cache-init) ISPN000079: Channel `ISPN` local address is `3ad955a78ecb-42249`, physical addresses are `[172.17.0.2:43808]` 2022-02-17 03:24:16,904 INFO [org.keycloak.connections.infinispan.DefaultInfinispanConnectionProviderFactory] (main) Node name: 3ad955a78ecb-42249, Site name: null 2022-02-17 03:24:17,408 ERROR [org.keycloak.services] (main) KC-SERVICES0010: Failed to add user 'kc-admin' to realm 'master': user with username exists 2022-02-17 03:24:17,799 INFO [io.quarkus] (main) Keycloak 17.0.0 on JVM (powered by Quarkus 2.7.0.Final) started in 6.964s. Listening on: https://0.0.0.0:8443 2022-02-17 03:24:17,800 INFO [io.quarkus] (main) Profile prod activated. 2022-02-17 03:24:17,800 INFO [io.quarkus] (main) Installed features: [agroal, cdi, hibernate-orm, infinispan-client, jdbc-h2, jdbc-mariadb, jdbc-mssql, jdbc-mysql, jdbc-oracle, jdbc-postgresql, keycloak, narayana-jta, reactive-routes, resteasy, resteasy-jackson, smallrye-context-propagation, smallrye-health, smallrye-metrics, vault, vertx] 2022-02-17 03:31:50,850 INFO [org.infinispan.CLUSTER] (Shutdown thread) ISPN000080: Disconnecting JGroups channel `ISPN` 2022-02-17 03:31:50,897 INFO [io.quarkus] (Shutdown thread) Keycloak stopped in 0.087s 2022-02-17 03:31:54,715 INFO [org.keycloak.quarkus.runtime.hostname.DefaultHostnameProvider] (main) Hostname settings: FrontEnd: <domain>, Strict HTTPS: true, Path: <request>, Strict BackChannel: false, Admin: <request> 2022-02-17 03:31:55,467 WARN [org.infinispan.PERSISTENCE] (keycloak-cache-init) ISPN000554: jboss-marshalling is deprecated and planned for removal 2022-02-17 03:31:55,489 WARN [org.infinispan.CONFIG] (keycloak-cache-init) ISPN000569: Unable to persist Infinispan internal caches as no global state enabled 2022-02-17 03:31:55,515 INFO [org.infinispan.CONTAINER] (keycloak-cache-init) ISPN000556: Starting user marshaller 'org.infinispan.jboss.marshalling.core.JBossUserMarshaller' 2022-02-17 03:31:55,707 INFO [org.infinispan.CONTAINER] (keycloak-cache-init) ISPN000128: Infinispan version: Infinispan 'Triskaidekaphobia' 13.0.5.Final 2022-02-17 03:31:55,847 INFO [org.infinispan.CLUSTER] (keycloak-cache-init) ISPN000078: Starting JGroups channel `ISPN` 2022-02-17 03:31:55,847 INFO [org.infinispan.CLUSTER] (keycloak-cache-init) ISPN000088: Unable to use any JGroups configuration mechanisms provided in properties {}. Using default JGroups configuration! 2022-02-17 03:31:55,908 WARN [org.jgroups.protocols.UDP] (keycloak-cache-init) JGRP000015: the send buffer of socket MulticastSocket was set to 1.00MB, but the OS only allocated 212.99KB 2022-02-17 03:31:55,909 WARN [org.jgroups.protocols.UDP] (keycloak-cache-init) JGRP000015: the receive buffer of socket MulticastSocket was set to 20.00MB, but the OS only allocated 212.99KB 2022-02-17 03:31:55,909 WARN [org.jgroups.protocols.UDP] (keycloak-cache-init) JGRP000015: the send buffer of socket MulticastSocket was set to 1.00MB, but the OS only allocated 212.99KB 2022-02-17 03:31:55,909 WARN [org.jgroups.protocols.UDP] (keycloak-cache-init) JGRP000015: the receive buffer of socket MulticastSocket was set to 25.00MB, but the OS only allocated 212.99KB 2022-02-17 03:31:57,918 INFO [org.jgroups.protocols.pbcast.GMS] (keycloak-cache-init) 3ad955a78ecb-30044: no members discovered after 2003 ms: creating cluster as coordinator 2022-02-17 03:31:57,926 INFO [org.infinispan.CLUSTER] (keycloak-cache-init) ISPN000094: Received new cluster view for channel ISPN: [3ad955a78ecb-30044|0] (1) [3ad955a78ecb-30044] 2022-02-17 03:31:57,929 INFO [org.infinispan.CLUSTER] (keycloak-cache-init) ISPN000079: Channel `ISPN` local address is `3ad955a78ecb-30044`, physical addresses are `[172.17.0.2:53471]` 2022-02-17 03:31:58,374 INFO [org.keycloak.connections.infinispan.DefaultInfinispanConnectionProviderFactory] (main) Node name: 3ad955a78ecb-30044, Site name: null 2022-02-17 03:31:59,519 INFO [org.keycloak.quarkus.runtime.storage.database.liquibase.QuarkusJpaUpdaterProvider] (main) Initializing database schema. Using changelog META-INF/jpa-changelog-master.xml 2022-02-17 03:32:21,554 INFO [org.keycloak.services] (main) KC-SERVICES0050: Initializing master realm 2022-02-17 03:32:23,707 INFO [org.keycloak.services] (main) KC-SERVICES0009: Added user 'admin' to realm 'master' 2022-02-17 03:32:23,938 INFO [io.quarkus] (main) Keycloak 17.0.0 on JVM (powered by Quarkus 2.7.0.Final) started in 31.647s. Listening on: https://0.0.0.0:8443 2022-02-17 03:32:23,938 INFO [io.quarkus] (main) Profile prod activated. 2022-02-17 03:32:23,938 INFO [io.quarkus] (main) Installed features: [agroal, cdi, hibernate-orm, infinispan-client, jdbc-h2, jdbc-mariadb, jdbc-mssql, jdbc-mysql, jdbc-oracle, jdbc-postgresql, keycloak, narayana-jta, reactive-routes, resteasy, resteasy-jackson, smallrye-context-propagation, smallrye-health, smallrye-metrics, vault, vertx] ``` ### How to Reproduce? _No response_ ### Anything else? ``` env: KEYCLOAK_ADMIN: "admin" KEYCLOAK_ADMIN_PASSWORD: "xxx" KC_DB_URL: "jdbc:mariadb://xxx:3306/keycloak" KC_DB_USERNAME: "keycloak" KC_DB_PASSWORD: "xxx" KC_DB: "mariadb" KC_HOSTNAME: "xxx" KC_HTTPS_CERTIFICATE_FILE: "/etc/x509/https/tls.crt" KC_HTTPS_CERTIFICATE_KEY_FILE: "/etc/x509/https/tls.key" ```

xgp · February 17, 2022, 2:44pm

The new default path in keycloak 17 is /. You can updated it to the old one with the --hostname-path=/auth flag.

glautervl · April 4, 2022, 3:56pm

Hi @xgp , after building and starting keycloak with --hostname-path=/auth flag and trying to open the Administration Console, I get redirected to http://localhost:8080/auth/admin/ which returns “Page not found”.

Any idea ?

xgp · April 4, 2022, 4:07pm

Send your whole startup command so that I can debug.

glautervl · April 4, 2022, 4:22pm

After ./kc.sh build --http-relative-path=/auth

I tried the below commands:
./kc.sh start-dev --http-port=8080 → New base path doesn’t take effect
./kc.sh start-dev --http-port=8080 --hostname-admin=/auth → it redirects to Page not found
./kc.sh start-dev --http-port=8080 --hostname-path=/auth → it redirects to blank page with errors on browser console
./kc.sh start-dev --http-port=8080 --hostname-path=/auth --hostname-admin=/auth → it redirects to blank page with errors on browser console

xgp · April 4, 2022, 4:39pm

try putting --http-relative-path=/auth in your start-dev command. AFAIK, running build has no effect on running start-dev. It is only for use before start

glautervl · April 4, 2022, 4:52pm

It worked
thank you @xgp

glautervl · April 5, 2022, 3:23pm

Hi @xgp.

The --http-relative-path=/auth flag is not accepted in production mode.

Any idea ?

xgp · April 5, 2022, 3:28pm

The build and start flags have to be used separately. If you look at the guide here Keycloak - Server - All configuration you will see a little tool icon next to --http-relative-path. That means you can either use it with build or start-dev. If you want your production setup to use --http-relative-path, you must first run it in build, and then start will use it.

My understanding is that the goal was to make startup time faster, but I’ve noticed here that how and where to use the configuration options is now a consistent source of confusion.

glautervl · April 5, 2022, 4:38pm

I understand the building process, before starting the application, no matter the mode I try to start, start-dev (development mode) or start (production mode) I always run kc.sh build --http-relative-path=/auth

I figured out the problem

I was running ./kc.sh start --hostname=www.mydomain.com --https-port=8181
It seems that for the frontend app the --https-port is ignored

After running:
./kc.sh start --hostname=www.mydomain.com:8181 --https-port=8181

Now everything is working properly when I try to access the Admin console.

Thanks for your help @xgp

soundsessential · April 6, 2022, 1:57am

Careful when you move to 17.0.1 - that port number after the host name is not supported anymore (apparently it shouldn’t actually work in 17.0.0), so you’ll likely need to make adjustments. Test before upgrading!

glautervl · April 6, 2022, 2:45pm

Hi @soundsessential, yes it is working fine for me on version 17.0.0.

If get any problem when moving to 17.0.1 I get back here.

Thank you