Hello, Thanks for the help, that flag was actually missing and it had to be done manually… I don’t know how is it expected to work without it… Docker generally supports no IPv6 AFAIK… From: Sebastian Laskawiec [mailto:slaskawi@redhat.com] Sent: Dienstag, 15. Januar 2019 09:52 To: Lukasz Lech <l.lech(a)ringler.ch&gt; Cc: keycloak-user(a)lists.jboss.org Subject: Re: [keycloak-user] Kubernetes: found IPv4 multicast address in an IPv6 stack Hey Lukasz, The clustering probably won't work in your setup. In other words, if you'd like to add another Keycloak node to ensure HA or balance the load, that won't work. I guess, you're using IPv4 network in your datacenter, aren't you? If so, please add -Djava.net.preferIPv4Stack=true switch to Keycloak to ensure, JGroups use IPv4. Thanks, Sebastian On Tue, Jan 15, 2019 at 9:22 AM Lukasz Lech <l.lech@ringler.ch<mailto:l.lech@ringler.ch>> wrote: Hello, I was succesfully running Keycloak as docker image (4.8.1), however, when I try to run in Kubernetes, I'm getting the following error: 07:53:34,742 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 52) MSC000001: Failed to start service org.wildfly.clustering.jgroups.channel.ee<http://org.wildfly.clustering.jgroups.channel.ee>: org.jboss.msc.service.StartException in service org.wildfly.clustering.jgroups.channel.ee<http://org.wildfly.clustering.jgroups.channel.ee>: java.lang.IllegalStateException: java.lang.Exception: found IPv4 multicast address /230.0.0.4<http://230.0.0.4> in an IPv6 stack at org.wildfly.clustering.service.FunctionalService.start(FunctionalService.java:70) at org.wildfly.clustering.service.AsyncServiceConfigurator$AsyncService.lambda$start$0(AsyncServiceConfigurator.java:117) at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) at java.lang.Thread.run(Thread.java:748) at org.jboss.threads.JBossThread.run(JBossThread.java:485) Caused by: java.lang.IllegalStateException: java.lang.Exception: found IPv4 multicast address /230.0.0.4<http://230.0.0.4> in an IPv6 stack at org.jboss.as.clustering.jgroups.subsystem.ChannelServiceConfigurator.get(ChannelServiceConfigurator.java:116) at org.jboss.as.clustering.jgroups.subsystem.ChannelServiceConfigurator.get(ChannelServiceConfigurator.java:58) at org.wildfly.clustering.service.FunctionalService.start(FunctionalService.java:67) ... 7 more Caused by: java.lang.Exception: found IPv4 multicast address /230.0.0.4<http://230.0.0.4> in an IPv6 stack at org.jgroups.stack.Configurator.setDefaultValues(Configurator.java:137) at org.jgroups.stack.ProtocolStack.init(ProtocolStack.java:829) at org.jgroups.JChannel.<init>(JChannel.java:200) at org.jboss.as.clustering.jgroups.JChannelFactory.createChannel(JChannelFactory.java:116) at org.jboss.as.clustering.jgroups.subsystem.ChannelServiceConfigurator.get(ChannelServiceConfigurator.java:96) ... 9 more Server seems to listen, going to / returns redirect to /auth, but going to /auth results in 404, no further error lands in logs... Anyone has any idea what it can be? Best regards, Lukasz Lech _______________________________________________ keycloak-user mailing list keycloak-user@lists.jboss.org<mailto:keycloak-user@lists.jboss.org> https://lists.jboss.org/mailman/listinfo/keycloak-user