Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-21856

Undertow won't accept wildcard address (0.0.0.0) for https

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Major Major
    • fuse-7.13-GA
    • fuse-7.12-GA
    • Karaf
    • None
    • False
    • None
    • False
    • Low
    • % %
    • Todo
    • Workaround Exists
    • Hide

      Don't use wildcard address works. 

          <interface name="secure">
      <w:inet-address value="127.0.0.1" />
    </interface>
      Show
      Don't use wildcard address works.      < interface name= "secure" >       <w:inet-address value= "127.0.0.1" />     </ interface >
    • Very Likely

      When configuring https for undertow.xml 

       

          <interface name="secure">
        <w:inet-address value="0.0.0.0" />
    </interface>

      will result a WARN: 

      2023-08-16 14:02:36,022 | WARN | (change controller) | .p.w.s.u.i.UndertowServerWrapper | 238 - org.ops4j.pax.web.pax-web-undertow - 8.0.20 | Listener defined in external configuration will be removed, because it's not enabled: AcceptingChannelWithAddress{acceptingChannel=io.undertow.protocols.ssl.UndertowAcceptingSslChannel@5a068658, address=/0.0.0.0:8183, secure=false}

       

       

      Documentation suggest to use wildcard address. 

      https://access.redhat.com/documentation/en-us/red_hat_fuse/7.12/html/apache_karaf_security_guide/webconsole#WebConsole-EnableTLS

      step 7. 

       

              ggrzybek Grzegorz Grzybek
              rhn-support-whui Roger Hui
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: