1 Reply Latest reply on Jul 5, 2019 4:34 AM by Jaikiran Pai

    Willdfly 17:Unable to Configure the Management Console for HTTPS in Standalone mode

    Ajay Sharma Newbie

      Hi,

       

      I am unable to configure the management console for https only in standalone mode.

      I followed steps given in 10.8. Configure the Management Console for HTTPS in Standalone mode - Red Hat Customer Portal

      But it is not working, deployments get stopped abruptly with no proper error message.

      Below is the snippet of my standalone.xml:-

       

      <management-interfaces>

                     <http-interface security-realm="ManagementRealm" ssl-context="httpsSSC">

                      <http-upgrade enabled="true"/>

                      <socket-binding https="management-https"/>

                  </http-interface>

      </management-interfaces>

       

      <socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}">

              <socket-binding name="management-https" interface="management" port="${jboss.management.https.port:9993}"/>

              <socket-binding name="ajp" port="${jboss.ajp.port:8009}"/>

              <socket-binding name="https" port="${jboss.https.port:8443}"/>

          </socket-binding-group>

       

      However, same format of standalone.xml is working fine on wildfly 10, 13 and 16. Changing "https" tag to "http" in "socket-binding" tag is opening management console on http.

      Please suggest the way forward.

       

      Br,

      Astha