[ https://issues.redhat.com/browse/WFLY-9641?page=com.atlassian.jira.plugin... ] Aliaksei Makarevich edited comment on WFLY-9641 at 2/28/20 3:37 AM: -------------------------------------------------------------------- [~gregoryhall994] Some information about configuration found here https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_ap... - the same solving is in forum thread (client-mapping) We have keycloak7.0.0-docker-cluster. We changed some cli files and mount them into containers. As for this case we change tools\cli\proxy.cli -- add line: /socket-binding-group=standard-sockets/socket-binding=http:write-attribute(name=client-mappings, value=[{destination-address=${jboss.host.name}}]) And without this, for exaple Keycloak 9.0.0 prints in log : WARN [org.jboss.as.ejb3.remote] (ClusterTopologyRegistrar - 1) WFLYEJB0509: Clustered EJBs in Node: bfc3539d1c33 are bound to INADDR_ANY(0.0.0.0). Either use a non-wildcard server bind address or add client-mapping entries to the relevant socket-binding for the Remoting connector was (Author: axelmak): [~gregoryhall994] Some information about configuration found here https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_ap... - the same solving is in forum thread (client-mapping) We have keycloak7.0.0-docker-cluster. We changed some cli files and mount them into containers. As for this case we change tools\cli\proxy.cli -- add line: /socket-binding-group=standard-sockets/socket-binding=http:write-attribute(name=client-mappings, value=[{destination-address=${jboss.host.name}}]) -- This message was sent by Atlassian Jira (v7.13.8#713008)