Fixing Web Console 404 Error in WildFly

This article will guide you in the resolution of the Error 404 (Page not found) when accessing WildFly Management Console. This is a generic error which can have different causes. In this article we will go step-by-step to find the cause and solve it.

Cause 1: WildFly Management Console on localhost

Firstly, out of the box WildFly publishes the management Interfaces on the loopback address:

<interface name="management">
            <inet-address value="${}"/>

Therefore, the most common cause could be that you are trying to access the Management Console of WildFly from a remote machine but you are exposing it only locally.

You can verify the current bindings by getting Wildly PID ( check this article to learn more about WildFly PID: How to check if JBoss is running? ) and running the following command:

$ netstat -tulpn | grep 14716

tcp        0      0*               LISTEN      14716/java          
tcp        0      0*               LISTEN      14716/java          
tcp        0      0*               LISTEN      14716/java          

As you can see, WildFly is running on localhost so you have to bind it an IP Address/Host to be accessed remotely. For example: -bmanagement= -Djboss.bind.address=

To learn more about changing WildFly IP Address check this article: How to bind WildFly to an IP address

Cause 2: WildFly Management Console on a different Port

Another common cause of the error 404 is that WildFly Management Console is running on a different port. You can still find useful the netstat command we have discussed to see which are the active ports.

In terms of configuration, you can set the management-http and management-https ports in the socket-binding-group section_

<socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}">
        <socket-binding name="ajp" port="${jboss.ajp.port:8009}"/>
        <socket-binding name="http" port="${jboss.http.port:8080}"/>
        <socket-binding name="https" port="${jboss.https.port:8443}"/>
        <socket-binding name="management-http" interface="management" port="${}"/>
        <socket-binding name="management-https" interface="management" port="${}"/>
        . . . .

Verify that the management port in the configuration correspond to the ports you are using. Also, consider the jboss.socket.binding.port-offset value. If you are setting it ( or overriding it at start-up), then you must access the management console at the correct value.

For example, if you are starting WildFly as follows:

./ -Djboss.socket.binding.port-offset=100

Then, you will be able to access the Management Console at: http://localhost:10090 (instead of localhost:9990) .

Cause 3: Admin Console Disabled

It is also possible that your system admin has disabled WildFly Admin Console. Therefore you will not be able to access it. This article discusses how to disable and re-enable the Admin Console: How to disable WildFly Admin Console

Other possible causes

There are still other possible causes of a 404 Error when accessing the Admin Console.

wildfly 404 error console

Before trying random solution, firstly check the server logs and confirm that WildFly Admin Console is listening:

20:05:06,631 INFO  [] (Controller Boot Thread) WFLYSRV0051: Admin console listening on

If you Admin Console is up and running, one of the most obvious is that you are getting a cached page from your browser. Try opening an incognito window of your browser or clear your browser’s cache and cookies. This can sometimes fix problems with the web browser that are causing error 404.

Also, there can be security restrictions or firewall settings may be preventing access to the web console. Check security settings and firewalls to ensure that they allow connections to the specified port. Much the same way, DNS resolution problems may prevent the correct mapping of the domain name to the server IP address.

By systematically checking these possible causes, you can identify and address the root issue leading to the HTTP 404 error when accessing the web console.