P2P works, but after third person joins JVB fails my setup on Azure Cloud

Please help me
My setup as below - in One VM Machine have a complete setup but in JVM i have stoped JVB and in other VM have JVB2 in jicofo log showing jvb2 connected but when third person join audio and video stoped.

Jvb2 sip property:
org.jitsi.videobridge.DISABLE_TCP_HARVESTER=true
org.jitsi.videobridge.ENABLE_STATISTICS=true
org.jitsi.videobridge.STATISTICS_TRANSPORT=muc
org.jitsi.videobridge.xmpp.user.shard.HOSTNAME=video.mashvirtual.info
org.jitsi.videobridge.xmpp.user.shard.DOMAIN=auth.video.mashvirtual.info
org.jitsi.videobridge.xmpp.user.shard.USERNAME=jvb
org.jitsi.videobridge.xmpp.user.shard.PASSWORD=B6Nw2mvN
org.jitsi.videobridge.xmpp.user.shard.MUC_JIDS=JvbBrewery@internal.auth.video.mashvirtual.info
org.jitsi.videobridge.xmpp.user.shard.MUC_NICKNAME=jvb2
org.jitsi.videobridge.xmpp.user.shard.DISABLE_CERTIFICATE_VERIFICATION=true

and jvb2 Log

OpenJDK 64-Bit Server VM warning: Ignoring option UseConcMarkSweepGC; support was removed in 14.0
2020-10-22 13:26:47.530 INFO: [1] JitsiConfig.#46: Initialized newConfig: merge of system properties,/etc/jitsi/videobridge/jvb.conf: 1,system properties,reference.conf @ jar:file:/usr/share/jitsi-videobridge/jitsi-videobridge.jar!/reference.conf: 1,reference.conf @ jar:file:/usr/share/jitsi-videobridge/lib/ice4j-3.0-22-g67ffceb.jar!/reference.conf: 1,reference.conf @ jar:file:/usr/share/jitsi-videobridge/lib/jitsi-media-transform-1.0-198-g1babb83.jar!/reference.conf: 1
2020-10-22 13:26:47.566 INFO: [1] ReadOnlyConfigurationService.reloadConfiguration#51: loading config file at path /etc/jitsi/videobridge/sip-communicator.properties
2020-10-22 13:26:47.568 INFO: [1] JitsiConfig.#67: Initialized legacyConfig: sip communicator props (no description provided)
2020-10-22 13:26:47.569 INFO: [1] JitsiConfig$Companion.reloadNewConfig#83: Reloading the Typesafe config source (previously reloaded 0 times).
2020-10-22 13:26:47.967 INFO: [12] org.ice4j.ice.harvest.MappingCandidateHarvesters.initialize:

Hi @khushiram.sharma, Can you attach some more logs for the community

1 Like

Sir, My setup on Azure Cloud - Complete Jitsi meet VM with all component and in other scalable VM installed jvb2.
when i stop jvb1 - P2P working but when join third person audio video stoped.
but when i check log jvb2 showing connected .

Please find the JVM and jvb2 logs.
jicofo.log (21.1 KB) jvb1.log (270.6 KB) jvb2.log (133.7 KB) jvb1-sip-communicator.properties.txt (744 Bytes) jvb2- sip-communicator.properties.txt (730 Bytes)

Check your port forwarding and firewall, for more details look at advanced section of https://jitsi.org/qi

1 Like

Sir, in VM firewall disabled and on Azure all TCP /UDP port enabled.

My setup on Azure Cloud - Complete Jitsi meet VM with all components and in other scalable VM installed jvb2.
when I stop jvb1 - P2P working but when join third-person audio-video stoped.
but when I check log jvb2 showing connected.

By connected you mean ice pairs succeeded?

1 Like

Check port forwarding for the second jvb and in its logs on startup that you see that it pickups its public address correctly.

1 Like

Sir jvb1-sip-communicator.properties.txt (744 Bytes) jvb2- sip-communicator.properties.txt (730 Bytes) jvb2.log (133.7 KB) jicofo.log (21.1 KB) jvb1.log (270.6 KB)

Dear Sir,

Please find the attached logs and sip conf

So jvb2 no pair succeeded its either public address is wrong, you need to check in the beginning of the logs or port forwarding not working for that instance

1 Like

jicofo.log (236.1 KB) jvb 2.log (454.9 KB)
Sir, Public ip is correct
jicofo.log (236.1 KB) jvb 2.log (454.9 KB) Uploading: jvb1.log… jvb1-sip-communicator.properties.txt (744 Bytes) jvb2- sip-communicator.properties.txt (741 Bytes)
in JV2

2020-10-23 11:11:10.082 INFO: [19] HealthChecker.run#170: Performed a successful health check in PT0.000009S. Sticky failure: false
2020-10-23 11:11:10.131 INFO: [18] VideobridgeExpireThread.expire#140: Running expire()
2020-10-23 11:11:10.131 INFO: [18] VideobridgeExpireThread.expire#146: Conference e8eb4d890a133714 should expire, expiring it
2020-10-23 11:11:10.132 INFO: [18] VideobridgeExpireThread.expire#146: Conference b8b7f0d3144acd40 should expire, expiring it
2020-10-23 11:11:10.133 INFO: [56] [confId=e8eb4d890a133714 gid=336675 conf_name=aa@conference.video.mashvirtual.info] Conference.expire#493: Expiring.
2020-10-23 11:11:10.133 INFO: [18] VideobridgeExpireThread.expire#146: Conference eca9f8416a667282 should expire, expiring it
2020-10-23 11:11:10.133 INFO: [56] [confId=e8eb4d890a133714 gid=336675 conf_name=aa@conference.video.mashvirtual.info] EndpointConnectionStatusMonitor.stop#58: Stopped
2020-10-23 11:11:10.134 INFO: [56] [confId=e8eb4d890a133714 gid=336675 conf_name=aa@conference.video.mashvirtual.info] Conference.updateStatisticsOnExpire#553: expire_conf,duration=47,has_failed=true,has_partially_failed=false
2020-10-23 11:11:10.134 INFO: [58] [confId=eca9f8416a667282 gid=336675 conf_name=aa@conference.video.mashvirtual.info] Conference.expire#493: Expiring.
2020-10-23 11:11:10.134 INFO: [58] [confId=eca9f8416a667282 gid=336675 conf_name=aa@conference.video.mashvirtual.info] EndpointConnectionStatusMonitor.stop#58: Stopped
2020-10-23 11:11:10.134 INFO: [58] [confId=eca9f8416a667282 gid=336675 conf_name=aa@conference.video.mashvirtual.info] Conference.updateStatisticsOnExpire#553: expire_conf,duration=27,has_failed=true,has_partially_failed=false
2020-10-23 11:11:10.135 INFO: [57] [confId=b8b7f0d3144acd40 gid=336675 conf_name=aa@conference.video.mashvirtual.info] Conference.expire#493: Expiring.
2020-10-23 11:11:10.135 INFO: [57] [confId=b8b7f0d3144acd40 gid=336675 conf_name=aa@conference.video.mashvirtual.info] EndpointConnectionStatusMonitor.stop#58: Stopped
2020-10-23 11:11:10.135 INFO: [57] [confId=b8b7f0d3144acd40 gid=336675 conf_name=aa@conference.video.mashvirtual.info] Conference.updateStatisticsOnExpire#553: expire_conf,duration=151,has_failed=true,has_partially_failed=false
2020-10-23 11:11:20.082 INFO: [19] HealthChecker.run#170: Performed a successful health check in PT0.000009S. Sticky failure: false
2020-10-23 11:11:30.082 INFO: [19] HealthChecker.run#170: Performed a successful health check in PT0.000011S. Sticky failure: false
2020-10-23 11:11:40.082 INFO: [19] HealthChecker.run#170: Performed a successful health check in PT0.00001S. Sticky failure: false
2020-10-23 11:11:50.082 INFO: [19] HealthChecker.run#170: Performed a successful health check in PT0.00001S. Sticky failure: false
2020-10-23 11:12:00.083 INFO: [19] HealthChecker.run#170: Performed a successful health check in PT0.000028S. Sticky failure: false
2020-10-23 11:12:10.082 INFO: [19] HealthChecker.run#170: Performed a successful health check in PT0.000008S. Sticky failure: false
2020-10-23 11:12:10.132 INFO: [18] VideobridgeExpireThread.expire#140: Running expire()

Sir above is fresh log and config file , but my problem still nor solved.

Kindly check attached log and configuration guide me

Dear Sir,
Any update on my problem

@khushiram.sharma

new Pair added: 10.0.0.5:10000/udp/host -> 192.168.0.4

something seems terribly wrong here. Your jvb2 seems to try to establish a connection to jvb1.

Sir, JVM and JVB1 installed in 192.168.0.4 and JVB2 installed in another VM

Prosody log

[C]: ?

Oct 23 11:14:02 portmanager error Error binding encrypted port for https: No key present in SSL/TLS configuration for https port 5281
Oct 23 11:14:02 portmanager error Error binding encrypted port for https: No key present in SSL/TLS configuration for https port 5281
Oct 23 13:03:52 portmanager error Error binding encrypted port for https: No key present in SSL/TLS configuration for https port 5281
Oct 23 13:03:52 portmanager error Error binding encrypted port for https: No key present in SSL/TLS configuration for https port 5281
Oct 23 13:27:18 portmanager error Error binding encrypted port for https: No key present in SSL/TLS configuration for https port 5281
Oct 23 13:27:18 portmanager error Error binding encrypted port for https: No key present in SSL/TLS configuration for https port 5281
Oct 23 14:05:31 portmanager error Error binding encrypted port for https: No key present in SSL/TLS configuration for https port 5281
Oct 23 14:05:31 portmanager error Error binding encrypted port for https: No key present in SSL/TLS configuration for https port 5281
Oct 23 16:10:38 portmanager error Error binding encrypted port for https: No key present in SSL/TLS configuration for https port 5281
Oct 23 16:10:38 portmanager error Error binding encrypted port for https: No key present in SSL/TLS configuration for https port 5281
Oct 23 16:15:21 portmanager error Error binding encrypted port for https: No key present in SSL/TLS configuration for https port 5281
Oct 23 16:15:21 portmanager error Error binding encrypted port for https: No key present in SSL/TLS configuration for https port 5281

Prosody logs are not relevant and those can be ignored.

Your jvb2 is getting its public address, if all pairs failed this means network issue and port 10000 UDP is not forwarded or is blocked by firewall.

1 Like

Sir, Please check the attached JVB logs, and please provide a resolution, All port enabled from nxg and firewall disabled for VMs,

jvb.log (1.3 MB)

your logs don’t make any sense to me.

Can you run on vm1:
ip a
sudo grep ADDRESS /etc/jitsi/videobridge/sip-communicator.properties

and the same on vm2

Sir , My problem has been resoved , when i enable health check prob in azure portal