Binding Wildfly's management interface to IP address fails ---------------------------------------------------------- Key: WFLY-6954 URL: https://issues.jboss.org/browse/WFLY-6954 Project: WildFly Issue Type: Bug Reporter: Eduard Dedu Assignee: Jason Greene Labels: Wildfly-10.0.0.Final Attachments: Screen Shot 2016-08-15 at 12.34.42.png Binding management interface to a remote IPV4 address causes the server to start with errors : Failed to start service jboss.network.management: org.jboss.msc.service.StartException in service jboss.network.management: WFLYSRV0082: failed to resolve interface management The error occurs if the server is started with the -b switch: ./standalone.sh -bmanagement=my_IPV4_address ... or if I edit the configuration standalone.xml: <interface name="management"> <inet-address value="${jboss.bind.address.management:my_IPV4_address}"/> </interface> The remote host located at the IPV4 address is up and running and responds to PING signals. TCP is enabled on port 9990. Wildfly starts w/o errors if I enable remote access from any host: ./standalone.sh -b 0.0.0.0 -bmanagement 0.0.0.0 & Perhaps I'm missing something, but this behaviour looks like a bug in a core WF feature.