How to bind WildFly to an IP address

This tutorial discusses how to set WildFly bind address using command line arguments and the configuration file. It applies to all WildFly versions and JBoss EAP as well.

WildFly application server and JBoss EAP include two network interfces . There are two interfaces: “public” and “management”:

        <interface name="management">
            <inet-address value="${}"/>
        <interface name="public">
            <inet-address value="${jboss.bind.address:}"/>
  • The “public” interface is used for all application related network communication.
  • The “management” interface is used for all components and services that are required by the management layer (i.e. the CLI or the Web Console).

By default, the “public” interface and the “management” interface are configured to listen on the loopback address of, as you can see from the following picture:

wildfly bind address jboss bind address

Therefore, in the default configuration, WildFly home page can be accessed at

The simplest way to change the “public” address is passing the -b argument while starting the server like:

$ ./ -c standalone-full.xml -b=

Please note that “-b” is an alias for the property “jboss.bind.address“:

$ ./ -Djboss.bind.address=

You can also hardcore the IP/Hostname in the XML configuration file. In this case, however, it is recommended to include as default the property jboss.bind.address and add, as fallback address, the hostname or IP Address:

<interface name="public">
    <inet-address value="${jboss.bind.address:}"/>

On the other hand, if you want bind also the WildFly’s management console, you can use the -bmanagement property as follows:

$ -bmanagement= -Djboss.bind.address=

Now you can connect to the CLI management interface using the IP Address:

$ ./ --connect controller=

Binding WildFly to all available IP Addresses

If you want to bind WildFly to all available IP addresses, then execute:

$ ./ -b=

You can also bind the “management” interface to all available IP addresses as:

$ ./ -bmanagement=

And of course, you can bind both interfaces as:

$ ./ -b= -bmanagement=

IMPORTANT: Binding JBoss to all IP addresses is not recommended for production systems due to a lack of security.

Binding WildFly with Docker

If you are running WildFly with Docker, then you can choose the bind address by passing the above properties to the Docker process as follows:

docker run -p 8080:8080 -p 9990:9990 -it jboss/wildfly /opt/jboss/wildfly/bin/ -bmanagement= -b

If you want to read how to configure the Port of WildFly, check this tutorial: Configuring port offset on JBoss AS / WildFly