Binding WildFly onto a custom IP

As for the port number, you might want to bind WildFly to an address different from the default one; for example, your public IP.

How to do it…

To achieve this kind of customization, you can use both the Web Console and the CLI. Nevertheless, it is common to have SSH access to the servers running WildFly, or worse (better for security reasons), you might have SSH on different servers before landing on the WildFly one. In this case, you will only be able to use the CLI, that's why from now on we will mainly use the CLI to manage the server.

Tip

Getting used to the CLI will give you a deeper knowledge of WildFly's configuration setting and it will be more mnemonic so you won't forget it.

Let's change the IP address as follows:

$ cd $WILDFLY_HOME
$ ./bin/standalone.sh -Djboss.bind.address=10.0.0.1
...
22:56:05,531 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0006: Undertow HTTP listener default listening on /10.0.0.1:8080
...

How it works…

If you look at standalone.xml, you will notice properties within the following {} and preceded by the dollar sign $. This property will be replaced by the value of the namesake parameter, specified when launching the server with the script.

There's more...

Furthermore, the same logic applies when you want to modify the management interface address. In that case, you will have to pass the jboss.bind.address.management parameter.

By the way, both parameters can be specified with shortcuts, such as -b 10.0.0.1 for the jboss.bind.address parameter, and -bmanagement 10.0.0.1 for the jboss.bind.address.management.