Jetty 443 Address already in use in latest stable


On the previous stable branch my was configured to serve everything on 443.

After upgrading to the latest stable videobridge, I am getting:

JVB 2018-09-26 20:12:18.122 WARNING: [10] org.eclipse.jetty.util.component.AbstractLifeCycle.setFailed() FAILED MuxServerConnector@42083d65{SSL-http/1.1}{:::443}: Address already in use
        at org.eclipse.jetty.server.AbstractNetworkConnector.doStart(

Is it possible the multiplexing of 443 is broken in the latest stable release, or that it has possibly been disabled for some reason?


Have you checked which other process is listening on port 443?


It appears to be the videobridge itself. If I kill the java process running the videobridge, then I can nc -l 443.


So when you killed it and restart jvb do you still see the same error?


Yes, every time.

I’m building in a docker container, so I built fresh with the apt packages being the version of the last stable release, and everything initializes correctly now.


I think I hit your problem.
Can you try enabling in jvb config org.ice4j.BIND_WILDCARD=true does that fixes it for you?


Hi Damencho, I’ll give it a try.


This should be fixed in the latest master.