Also I tried writting the external ip in the management interface (in standalone-full.xml), and once jboss started, I tried to connect by cli in this way:
sh jboss-cli.sh --controller=[ip]:9990 and then connect. It looks like the connect was successfully as the error message does not appear, however the jboss server dies after that, I mean, thr http://[ip]:8080 and http://[ip]:9990 stop working.
I understand the -b command line switch just binds to the
jboss.bind.address. If you want to change the
jboss.bind.address.management as well you should use the -b<name> switch like:
standalone.sh -b 0.0.0.0 -bmanagement 0.0.0.0
You should then check your server.log. It should show something like:
WFLYSRV0060: Http management interface listening on http://0.0.0.0:9990/management
Thanks for your answer. I tried that, it looks like the connect command is successfully:
[trauriger@bellidov bin]$ sh jboss-cli.sh
You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands.
[disconnected /] connect
However, when I tried any cli command, I receive this message:
Failed to get the AS release info: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://localhost:9990. The connection failed
At the same time the server stops working. In the logs I saw this:
standalone.sh: line 307: 30794 Killed "java" -D"[Standalone]" -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true "-Dorg.jboss.boot.log.file=/home/trauriger/wildfly-11.0.0.Alpha1/standalone/log/server.log" "-Dlogging.configuration=file:/home/trauriger/wildfly-11.0.0.Alpha1/standalone/configuration/logging.properties" -jar "/home/trauriger/wildfly-11.0.0.Alpha1/jboss-modules.jar" -mp "/home/trauriger/wildfly-11.0.0.Alpha1/modules" org.jboss.as.standalone -Djboss.home.dir="/home/trauriger/wildfly-11.0.0.Alpha1" -Djboss.server.base.dir="/home/trauriger/wildfly-11.0.0.Alpha1/standalone" '-c' 'standalone-full.xml' '-b' '0.0.0.0' '-bmanagement' '0.0.0.0'
Has anyone got any idea why this is happening? Thanks.
It looks like there is some other issue with your WildFly configuration.
You should therefore investigate your startup for any error messages.
Maybe you could also post your server.log.