Wildfly Remote Administration Console not working

Question

I am new to WildFly / JBOSS. I am using WildFly 8.2.0. I installed it as a service on Linux using the installation script from http://sukharevd.net/wildfly-8-installation.html . Everything is working fine. I connect to my Linux remotely using SSH. It does not have a GUI. Therefore, I need to be able to remotely connect to the administration console. I cannot connect and displays the following message:

"Automatic redirection to the Administration Console is currently not available. Most likely, this is due to the fact that the Administration Console is displayed on a network interface different from the one to which you are connected."

I see the same problem mentioned in the following link

https://github.com/jboss-dockerfiles/wildfly/issues/3

The link has a solution, but uses a docker. How can I do this without using dockers? I am using a standalone configuration. What configuration do I need to change?

Answer 1

You must start WildFly using the following command. Using 0.0.0.0 will associate WildFly with all available IP addresses in your Linux window. If you want to bind to a specific IP address; you can replace 0.0.0.0 with the corresponding IP address.

$WILDFLY_HOME/bin/standalone.sh -b=0.0.0.0 -bmanagement=0.0.0.0

EDIT: after installation is complete with a script. We have to go to /etc/init.d/service and change JBOSS_SCRIPT = $ JBOSS_HOME / bin / standalone.sh to JBOSS_SCRIPT = "$ JBOSS_HOME / bin / standalone.sh -b = 0.0.0.0 -bmanagement = 0.0.0.0"

Answer 2

The best approach is to edit JBOSS_HOME / standalone / configuration / standalone.xml, edit the code snippet, and change the address to 0.0.0.0.

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

Answer 3

Second possible solution

As an alternative to adding parameters, run the start command, you can edit your standalone.xml to enable remote access from any source. This approach is more useful if you need remote access in most cases, so you do not need to remember to pass additional parameters to the start command, as shown above.

First go to the Wildfly configuration folder:

terminal

 cd /opt/wildfly-8.2.0.Final/standalone/configuration 

Then edit the standalone.xml file using the desired file editor and make the following changes: Replace this:

standalone.xml

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

Wherein:

standalone.xml

 <interface name="management"> <any-address/> </interface> <interface name="public"> <any-address/> </interface> 

Be sure to save the changes and restart Wildfly:

at the terminal

 /opt/wildfly-8.2.0.Final/bin/jboss-cli.sh --connect --command=:reload 

Done.