I already setup a self-host server A with JMS and JVB together, and it can work for conference call successfully
Then I setup additional JVB on another server B, the new JVB can successfully register to JMS on server A. but when I stop the JVB on server A and only use the new JVB on server B to setup conference call, it failed.
The issue is that every endpoint can join the conference but can not receive remote endpoints’s video and audio, and following errors on chrome console are reported and a web notification show up as below screen-shot.
Would you please check these errors and help to share your suggestion how to debug it, Thanks in advance.
====chrome console errors====
Logger.js:154 2023-01-08T03:22:27.929Z [modules/RTC/BridgeChannel.js] <WebSocket.e.onclose>: Channel closed: 1006
r @ Logger.js:154
e.onclose @ BridgeChannel.js:424
BridgeChannel.js:87 WebSocket connection to ‘wss://jitsi.domain.com/colibri-ws/default-id/6e3648854f7eca12/91043086?pwd=2rmasikskj6hac7p2bbusscem1’ failed:
_initWebSocket @ BridgeChannel.js:87
t @ BridgeChannel.js:106
Logger.js:154 2023-01-08T03:22:30.343Z [modules/RTC/BridgeChannel.js] <WebSocket.e.onclose>: Channel closed by server
Logger.js:154 2023-01-08T03:22:30.343Z [modules/RTC/BridgeChannel.js] <WebSocket.e.onclose>: Channel closed: 1006
r @ Logger.js:154
e.onclose @ BridgeChannel.js:424
BridgeChannel.js:87 WebSocket connection to ‘wss://jitsi.domain.com/colibri-ws/default-id/6e3648854f7eca12/91043086?pwd=48mdh9gam6u0tinces1ov7k59t’ failed:
_initWebSocket @ BridgeChannel.js:87
t @ BridgeChannel.js:106
Logger.js:154 2023-01-08T03:22:47.782Z [modules/RTC/BridgeChannel.js] <WebSocket.e.onclose>: Channel closed by server
I am still struggling on this error, and when i grep jvb.log on issue server B, I noticed below two error log info, not sure whether you have any experience on what’s going wrong about them:
====ISSUE2====
java.lang.Exception: Address discovery through STUN failed
at org.jitsi.videobridge.health.JvbHealthChecker.check(JvbHealthChecker.kt:39)
at org.jitsi.videobridge.health.JvbHealthChecker.access$check(JvbHealthChecker.kt:25)
at org.jitsi.videobridge.health.JvbHealthChecker$healthChecker$1.invoke(JvbHealthChecker.kt:31)
at org.jitsi.videobridge.health.JvbHealthChecker$healthChecker$1.invoke(JvbHealthChecker.kt:31)
at org.jitsi.health.HealthChecker.run(HealthChecker.kt:144)
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$1.run(RecurringRunnableExecutor.java:328)
It looks like JVB cannot find its external IP. Do you disable or update STUN_MAPPING_HARVESTER_ADDRESSES in /etc/jitsi/videobridge/sip-communicator.properties?
I cat my /etc/jitsi/videobridge/sip-communicator.properties in my issue server B, please check below info for that.
I copy this file from the jvb of server A which can work well and only change the nickname and add org.jitsi.videobridge.xmpp.user.shard-1.DISABLE_CERTIFICATE_VERIFICATION=true
