JVB healthcheck failed or not found

As I said you will be able to use more than 3 users if those users are in the same network as the bridge. Otherwise you need to follow this to configure it: https://github.com/jitsi/jitsi-meet/blob/master/doc/quick-install.md#advanced-configuration

Well - thanks for trying. I have tried on both Ubuntu16 and Ubuntu18 and can’t get it working on either. Oh well. Best of luck with this project. I am out.

@damencho
it stilll can’t run more than 3 users in the same local network 192.168.9.xxx. , below is the jvb log, any error with it?
JVB 2019-05-17 20:47:37.296 WARNING: [15] org.jitsi.videobridge.EndpointMessageTransport.log() SCTP connection with d9c9d7c8527f6fa0 not ready yet.
JVB 2019-05-17 20:47:37.296 WARNING: [15] org.jitsi.videobridge.EndpointMessageTransport.log() No available transport channel, can’t send a message
JVB 2019-05-17 20:47:37.309 INFO: [18] org.jitsi.videobridge.health.Health.log() Performed a successful health check in 15ms. Sticky failure: false
JVB 2019-05-17 20:47:46.632 FINE: [170] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Processing IQ (packetId gIage-48):
JVB 2019-05-17 20:47:47.310 INFO: [18] org.jitsi.videobridge.Videobridge.log() CAT=stat create_conf,conf_id=7007c4d68bef8fe7 conf_name=null,logging=false,conf_count=1,ch_count=0,v_streams=0
JVB 2019-05-17 20:47:47.326 INFO: [18] org.jitsi.videobridge.health.Health.log() Performed a successful health check in 17ms. Sticky failure: false
JVB 2019-05-17 20:47:56.231 INFO: [17] org.jitsi.videobridge.VideobridgeExpireThread.log() Running expire()
JVB 2019-05-17 20:47:56.631 FINE: [194] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Processing IQ (packetId gIage-50):
JVB 2019-05-17 20:47:57.327 INFO: [18] org.jitsi.videobridge.Videobridge.log() CAT=stat create_conf,conf_id=346b405653a29664 conf_name=null,logging=false,conf_count=1,ch_count=0,v_streams=0
JVB 2019-05-17 20:47:57.359 INFO: [18] org.jitsi.videobridge.health.Health.log() Performed a successful health check in 33ms. Sticky failure: false
JVB 2019-05-17 20:48:06.632 FINE: [217] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Processing IQ (packetId gIage-52):
JVB 2019-05-17 20:48:07.361 INFO: [18] org.jitsi.videobridge.Videobridge.log() CAT=stat create_conf,conf_id=1a0ddc12c0fd2a67 conf_name=null,logging=false,conf_count=1,ch_count=0,v_streams=0
JVB 2019-05-17 20:48:07.380 INFO: [18] org.jitsi.videobridge.health.Health.log() Performed a successful health check in 19ms. Sticky failure: false
JVB 2019-05-17 20:48:16.632 FINE: [240] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Processing IQ (packetId gIage-54):

@zhouyinfei what about port udp 10000, is it open on the firewall?
Clients from the same network should be able to access directly the bridge address and port 192.168.9.XX:10000.

The firewall is closed , 10000 port should be accessible from the same network

@damencho
I faced same errors likes above and my java version is openjdk version “1.8.0_212” , any ideas ?

JVB 2019-05-30 12:32:24.793 SEVERE: [26] org.ice4j.socket.jdk8.DelegatingServerSocketChannel.() Cannot find method translateInterestOps
java.lang.NoSuchMethodException: sun.nio.ch.SelChImpl.translateInterestOps(int)
at java.lang.Class.getMethod(Class.java:1786)
at org.ice4j.socket.jdk8.DelegatingServerSocketChannel.(DelegatingServerSocketChannel.java:97)
at org.ice4j.socket.jdk8.MuxServerSocketChannel.(MuxServerSocketChannel.java:110)
at org.ice4j.socket.jdk8.MuxingServerSocketChannel.createMuxServerSocketChannel(MuxingServerSocketChannel.java:767)
at org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(MuxingServerSocketChannel.java:305)
at org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(MuxServerSocketChannel.java:64)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindMuxServerSocketChannel(MuxServerSocketChannelFactory.java:181)
at org.ice4j.ice.harvest.AbstractTcpListener.addSocketChannel(AbstractTcpListener.java:443)
at org.ice4j.ice.harvest.AbstractTcpListener.init(AbstractTcpListener.java:425)
at org.ice4j.ice.harvest.AbstractTcpListener.(AbstractTcpListener.java:271)
at org.ice4j.ice.harvest.AbstractTcpListener.(AbstractTcpListener.java:255)
at org.ice4j.ice.harvest.TcpHarvester.(TcpHarvester.java:127)
at org.jitsi.videobridge.IceUdpTransportManager.initializeStaticConfiguration(IceUdpTransportManager.java:295)
at org.jitsi.videobridge.IceUdpTransportManager.configureHarvesters(IceUdpTransportManager.java:793)
at org.jitsi.videobridge.IceUdpTransportManager.createIceAgent(IceUdpTransportManager.java:1074)
at org.jitsi.videobridge.IceUdpTransportManager.(IceUdpTransportManager.java:566)
at org.jitsi.videobridge.IceUdpTransportManager.(IceUdpTransportManager.java:527)
at org.jitsi.videobridge.SctpConnection.createTransportManager(SctpConnection.java:337)
at org.jitsi.videobridge.Channel.initialize(Channel.java:674)
at org.jitsi.videobridge.Content.createSctpConnection(Content.java:412)
at org.jitsi.videobridge.health.Health.check(Health.java:184)
at org.jitsi.videobridge.health.Health.doCheck(Health.java:244)
at org.jitsi.videobridge.health.Health.doRun(Health.java:495)
at org.jitsi.utils.concurrent.PeriodicRunnableWithObject.run(PeriodicRunnableWithObject.java:89)
at org.jitsi.utils.concurrent.RecurringRunnableExecutor.run(RecurringRunnableExecutor.java:216)
at org.jitsi.utils.concurrent.RecurringRunnableExecutor.runInThread(RecurringRunnableExecutor.java:292)
at org.jitsi.utils.concurrent.RecurringRunnableExecutor.access$000(RecurringRunnableExecutor.java:36)
at org.jitsi.utils.concurrent.RecurringRunnableExecutor$1.run(RecurringRunnableExecutor.java:328)

The exception is normal and will be removed in the following versions/updates, you can ignore it.