I deployed wildfly 14 & Nginx on a pre-prodction server.Where Nginx is a reverse proxy. and I forced wildfly to use the ssl throught the 443 by adding a socket-binding

    <socket-binding-group name="standard-sockets" default-interface="public">
      <socket-binding name="https-external" port="443"/>

and I modified the http-listener

<http-listener name="default" socket-binding="http" redirect-socket="https" enable-http2="true"/>

when I scan the server for the opened ports I found this result:

80/tcp   open     http
443/tcp  open     https
445/tcp  filtered microsoft-ds
8080/tcp open     http-proxy
8443/tcp open     https-alt

so how can I stop wildfly from listening on 8080 and 8443 whiout causing any damage and keeping the admin console accessible?

  • Are you sure that nginx is not listening on 443? If it does, then Wildfly will try to bind on the defined port (443 in your case) and if the port is in use, I suppose it will bind to 8443. No idea how wildfly works or behaves but from my little experience with Java Apps, that might be a common scenario Feb 4, 2019 at 15:02
  • run this as root to find out which processes are binding to which ports: netstat -ntlpe, paste the output here so that we can be sure what to answer.
    – Marcel
    Feb 4, 2019 at 15:14
  • this is the result of netstat -tulpn tcp 0 0* LISTEN 2303/java tcp 0 0* LISTEN 2303/java tcp 0 0* LISTEN 1460/nginx -g daemo tcp 0 0* LISTEN 2303/java tcp 0 0* LISTEN 1460/nginx -g daemo
    – Barttttt
    Feb 4, 2019 at 15:16
  • Ok, so you see the output? There's a java process binding on all interfaces &&, which I suppose is the mentioned wildfly. You should instruct wildfly to bind only to the loopback device, and then have the reverse proxy bind on the loopback, and only letting nginx to bind to the public interface.
    – Marcel
    Feb 4, 2019 at 15:32
  • that's right the java process are those of the wildfly , but how can instruct wildfly to listen to the loopback device ?
    – Barttttt
    Feb 4, 2019 at 15:39

1 Answer 1


OK, here it is:


This piece of documentation states there's a XML section like this:

  <interface name="management">
   <inet-address value=""/>
  <interface name="public">
   <inet-address value=""/>

Just look if inet-address for both public and management interfaces are set to the value above, and I think you'll have it working as expected.

  • Thnaks Marcel! you saved me!
    – Barttttt
    Feb 4, 2019 at 17:42

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.