-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Video Quality Impaired - The bridge Channel has been disconnect #1599
Comments
The problem is caused by the users not being able to reach the JVB. Did you set JVB_ADVERTISED_IPS to a correct value? |
I'm running into a VPS with public ip, I did set the JVB_ADVERTISED_IPS to the public ip, should I set to a different one? |
That should be ok. Is port 10000 filtered somehow? |
I'm using behind Nginx Proxy Manager, I'm forwarding the 8000 and using SSL with nginx, the ports are openned also in the Firewall, 10000 its openned too |
Port 10000 needs to be open for UDP traffic too, is that the case? |
Port 10000 Its already openned |
Then we need the browser console logs to further diagnose. |
Error: 2023-09-12T18:02:08.554Z [modules/RTC/BridgeChannel.js] <e.onclose>: Channel closed: 1001 endpoint closed Warning: MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 rtc.forwarded_sources_changed listeners added. Use emitter.setMaxListeners() to increase limit |
Check the network tab to see the WS connection attempt. |
Yes. I think it might be triggered by an ICE failure. Can you please share the full JS console logs? |
Are you using some kind of reverse proxy? |
Yes, as I said before I'm using Nginx Proxy Manager (also in docker) that version that we use a web GUI. I checked and I'm using the 8000 port to http to my jitsi and also I enabled websocket support. Also my domain is from Cloudflare, do you know if maybe is there some config to adjust there? I saw that in jitsi doc only there is a thing talking about reversy proxy but using the manually bare metal nginx and nothing about Nginx Proxy Manager docker (https://nginxproxymanager.com) |
Sorry I had missed the context. I have no experience with nginx proxy manager. You can turn off colibri WS and enable SCTP, that should work. |
Thank you, I saw in the Documentation this settings: ENABLE_SCTP=1 Where should I add that? I'm using docker version |
In your .env file |
I added in the .env But I had the same problem showed in the js logs |
Can you please share the full logs? |
How can I get the full logs? Update: deleted everything and rebuild with the latest version and the got the same problem |
The full JS console logs. |
I'm trying to but I don't know how. How can I get the full JS console logs? isnt it that logs I've sent before? |
In that screen, select all log levels and copy the text. |
logs: docker-jitsi-meet-prosody-1 | 2023-10-21 20:16:01 c2s55708054a090 info Client connected
docker-jitsi-meet-prosody-1 | 2023-10-21 20:16:02 c2s55708054a090 info Authenticated as [email protected]
docker-jitsi-meet-jicofo-1 | Jicofo 2023-10-21 20:16:02.280 INFO: [43] ConferenceIqHandler.handleConferenceIq#85: Conference request for room [email protected], from [email protected]/wbq77OdG-EVz
docker-jitsi-meet-jicofo-1 | Jicofo 2023-10-21 20:16:02.396 INFO: [43] [xmpp_connection=client] XmppProvider.discoverFeatures#248: Discovered features for [email protected]/a9efe561 in 0 ms.
docker-jitsi-meet-jicofo-1 | Jicofo 2023-10-21 20:16:02.397 INFO: [43] [room[email protected] meeting_id=8036ac00-542a-4b51-b238-281b2031c0fe] JitsiMeetConferenceImpl.onMemberJoined#728: Member joined:a9efe561 stats-id=Ezekiel-H3K region=null audioMuted=true videoMuted=true role=PARTICIPANT isJibri=false isJigasi=false isTranscriber=false, room=main
docker-jitsi-meet-jicofo-1 | Jicofo 2023-10-21 20:16:02.397 INFO: [43] [room[email protected] meeting_id=8036ac00-542a-4b51-b238-281b2031c0fe] JitsiMeetConferenceImpl.inviteChatMember#790: Creating participant 820c2b6e with features=[XMPP_CAPS, JSON_SOURCES, RECEIVE_MULTIPLE_STREAMS, REMB, SOURCE_NAMES, TCC, VISITORS_V1, E2EE, RTX, JINGLE, DTLS, JINGLE_RTP, AUDIO, VIDEO, SCTP, JINGLE_ICE, RAYO]
docker-jitsi-meet-jicofo-1 | Jicofo 2023-10-21 20:16:02.398 INFO: [43] [room[email protected] meeting_id=8036ac00-542a-4b51-b238-281b2031c0fe] JitsiMeetConferenceImpl.inviteChatMember#790: Creating participant a9efe561 with features=[XMPP_CAPS, JSON_SOURCES, RECEIVE_MULTIPLE_STREAMS, REMB, SOURCE_NAMES, TCC, VISITORS_V1, RTX, JINGLE, DTLS, JINGLE_RTP, AUDIO, VIDEO, SCTP, JINGLE_ICE, RAYO]
docker-jitsi-meet-jicofo-1 | Jicofo 2023-10-21 20:16:02.399 INFO: [44] [room[email protected] meeting_id=8036ac00-542a-4b51-b238-281b2031c0fe] ColibriV2SessionManager.allocate#276: Allocating for 820c2b6e
docker-jitsi-meet-jicofo-1 | Jicofo 2023-10-21 20:16:02.399 INFO: [44] BridgeSelectionStrategy.select#114: Selected initial bridge Bridge[[email protected]/8c817ce15e2a, version=2.3.44-g8983b11f, relayId=null, region=null, stress=0.00] with reported stress=0.0 for participantProperties=ParticipantProperties(region=null, visitor=false) using strategy SingleBridgeSelectionStrategy
docker-jitsi-meet-jicofo-1 | Jicofo 2023-10-21 20:16:02.400 INFO: [46] [room[email protected] meeting_id=8036ac00-542a-4b51-b238-281b2031c0fe] ColibriV2SessionManager.allocate#276: Allocating for a9efe561
docker-jitsi-meet-jicofo-1 | Jicofo 2023-10-21 20:16:02.400 INFO: [44] [room[email protected] meeting_id=8036ac00-542a-4b51-b238-281b2031c0fe] ColibriV2SessionManager.allocate#322: Selected 8c817ce15e2a, session exists: false
docker-jitsi-meet-jicofo-1 | Jicofo 2023-10-21 20:16:02.401 INFO: [46] BridgeSelectionStrategy.select#127: Existing bridge does not have a relay, will not consider other bridges.
docker-jitsi-meet-jicofo-1 | Jicofo 2023-10-21 20:16:02.401 INFO: [46] [room[email protected] meeting_id=8036ac00-542a-4b51-b238-281b2031c0fe] ColibriV2SessionManager.allocate#322: Selected 8c817ce15e2a, session exists: true
docker-jitsi-meet-jvb-1 | JVB 2023-10-21 20:16:02.409 INFO: [30] [confId=50ec61216d4a45e9 conf_name[email protected] meeting_id=8036ac00] EndpointConnectionStatusMonitor.start#58: Starting connection status monitor
docker-jitsi-meet-jvb-1 | JVB 2023-10-21 20:16:02.410 INFO: [30] Videobridge.createConference#283: create_conf, id=50ec61216d4a45e9 meeting_id=8036ac00-542a-4b51-b238-281b2031c0fe
docker-jitsi-meet-jvb-1 | JVB 2023-10-21 20:16:02.413 INFO: [79] [confId=50ec61216d4a45e9 conf_name[email protected] meeting_id=8036ac00 epId=820c2b6e local_ufrag=a3cko1hdaf83fc ufrag=a3cko1hdaf83fc] Agent.gatherCandidates#647: Gathering candidates for component stream-820c2b6e.RTP.
docker-jitsi-meet-jvb-1 | JVB 2023-10-21 20:16:02.425 INFO: [79] [confId=50ec61216d4a45e9 conf_name[email protected] meeting_id=8036ac00 epId=820c2b6e] Endpoint.<init>#334: Created new endpoint isUsingSourceNames=true, iceControlling=true
docker-jitsi-meet-jvb-1 | JVB 2023-10-21 20:16:02.431 INFO: [79] [confId=50ec61216d4a45e9 conf_name[email protected] meeting_id=8036ac00 epId=a9efe561 local_ufrag=d43jg1hdaf83fu ufrag=d43jg1hdaf83fu] Agent.gatherCandidates#647: Gathering candidates for component stream-a9efe561.RTP.
docker-jitsi-meet-jicofo-1 | Jicofo 2023-10-21 20:16:02.435 INFO: [44] [room[email protected] meeting_id=8036ac00-542a-4b51-b238-281b2031c0fe participant=820c2b6e] ParticipantInviteRunnable.doInviteOrReinvite#386: Sending session-initiate to: [email protected]/820c2b6e sources={jvb=[audio=[575684608], video=[2197643558], groups=[]]}
docker-jitsi-meet-jvb-1 | JVB 2023-10-21 20:16:02.438 INFO: [79] [confId=50ec61216d4a45e9 conf_name[email protected] meeting_id=8036ac00 epId=a9efe561] Endpoint.<init>#334: Created new endpoint isUsingSourceNames=true, iceControlling=true
docker-jitsi-meet-jicofo-1 | Jicofo 2023-10-21 20:16:02.446 INFO: [46] [room[email protected] meeting_id=8036ac00-542a-4b51-b238-281b2031c0fe participant=a9efe561] ParticipantInviteRunnable.doInviteOrReinvite#386: Sending session-initiate to: [email protected]/a9efe561 sources={jvb=[audio=[575684608], video=[2197643558], groups=[]]}
docker-jitsi-meet-jvb-1 | JVB 2023-10-21 20:16:02.645 INFO: [79] [confId=50ec61216d4a45e9 conf_name[email protected] meeting_id=8036ac00 epId=820c2b6e stats_id=Velda-5V8] AllocationSettingsWrapper.setBandwidthAllocationSettings#174: Ignoring assumed-bandwidth-bps, not allowed in config.
docker-jitsi-meet-jvb-1 | JVB 2023-10-21 20:16:02.648 INFO: [79] [confId=50ec61216d4a45e9 conf_name[email protected] meeting_id=8036ac00 epId=820c2b6e stats_id=Velda-5V8] AllocationSettingsWrapper.setBandwidthAllocationSettings#174: Ignoring assumed-bandwidth-bps, not allowed in config.
docker-jitsi-meet-jvb-1 | JVB 2023-10-21 20:16:02.649 INFO: [79] [confId=50ec61216d4a45e9 conf_name[email protected] meeting_id=8036ac00 epId=820c2b6e stats_id=Velda-5V8] AllocationSettingsWrapper.setBandwidthAllocationSettings#174: Ignoring assumed-bandwidth-bps, not allowed in config.
docker-jitsi-meet-jicofo-1 | Jicofo 2023-10-21 20:16:03.344 INFO: [46] [room[email protected] meeting_id=8036ac00-542a-4b51-b238-281b2031c0fe participant=a9efe561] Participant$JingleRequestHandlerImpl.onSessionOrTransportAccept#474: Received session-accept
docker-jitsi-meet-jicofo-1 | Jicofo 2023-10-21 20:16:03.346 INFO: [46] [room[email protected] meeting_id=8036ac00-542a-4b51-b238-281b2031c0fe] ColibriV2SessionManager.updateParticipant#548: Updating a9efe561 with transport=org.jitsi.xmpp.extensions.jingle.IceUdpTransportPacketExtension@31fe52c, sources=[audio=[4136810578], video=[921552061, 2989166995, 3273004608, 1400283641, 285635843, 4199804272], groups=[FID[921552061, 2989166995], SIM[921552061, 3273004608, 1400283641], FID[3273004608, 285635843], FID[1400283641, 4199804272]]]
docker-jitsi-meet-jicofo-1 | Jicofo 2023-10-21 20:16:03.346 INFO: [46] [room[email protected] meeting_id=8036ac00-542a-4b51-b238-281b2031c0fe] JitsiMeetConferenceImpl.acceptSession#1318: Accepted initial sources from a9efe561: [audio=[4136810578], video=[921552061, 2989166995, 3273004608, 1400283641, 285635843, 4199804272], groups=[FID[921552061, 2989166995], SIM[921552061, 3273004608, 1400283641], FID[3273004608, 285635843], FID[1400283641, 4199804272]]]
docker-jitsi-meet-jvb-1 | JVB 2023-10-21 20:16:03.352 INFO: [79] [confId=50ec61216d4a45e9 conf_name[email protected] meeting_id=8036ac00 epId=a9efe561 stats_id=Ezekiel-H3K] DtlsTransport.setSetupAttribute#126: The remote side is acting as DTLS client, we'll act as server
docker-jitsi-meet-jvb-1 | JVB 2023-10-21 20:16:03.352 INFO: [79] [confId=50ec61216d4a45e9 conf_name[email protected] meeting_id=8036ac00 epId=a9efe561 stats_id=Ezekiel-H3K local_ufrag=d43jg1hdaf83fu] IceTransport.startConnectivityEstablishment#204: Starting the Agent without remote candidates.
docker-jitsi-meet-jvb-1 | JVB 2023-10-21 20:16:03.353 INFO: [79] [confId=50ec61216d4a45e9 conf_name[email protected] meeting_id=8036ac00 epId=a9efe561 stats_id=Ezekiel-H3K local_ufrag=d43jg1hdaf83fu ufrag=d43jg1hdaf83fu] Agent.startConnectivityEstablishment#736: Start ICE connectivity establishment.
docker-jitsi-meet-jvb-1 | JVB 2023-10-21 20:16:03.353 INFO: [79] [confId=50ec61216d4a45e9 conf_name[email protected] meeting_id=8036ac00 epId=a9efe561 stats_id=Ezekiel-H3K local_ufrag=d43jg1hdaf83fu ufrag=d43jg1hdaf83fu] Agent.initCheckLists#972: Init checklist for stream stream-a9efe561
docker-jitsi-meet-jvb-1 | JVB 2023-10-21 20:16:03.354 INFO: [79] [confId=50ec61216d4a45e9 conf_name[email protected] meeting_id=8036ac00 epId=a9efe561 stats_id=Ezekiel-H3K local_ufrag=d43jg1hdaf83fu ufrag=d43jg1hdaf83fu] Agent.setState#946: ICE state changed from Waiting to Running.
docker-jitsi-meet-jvb-1 | JVB 2023-10-21 20:16:03.355 INFO: [79] [confId=50ec61216d4a45e9 conf_name[email protected] meeting_id=8036ac00 epId=a9efe561 stats_id=Ezekiel-H3K local_ufrag=d43jg1hdaf83fu] IceTransport.iceStateChanged#347: ICE state changed old=Waiting new=Running
docker-jitsi-meet-jvb-1 | JVB 2023-10-21 20:16:03.355 INFO: [79] [confId=50ec61216d4a45e9 conf_name[email protected] meeting_id=8036ac00 epId=a9efe561 stats_id=Ezekiel-H3K local_ufrag=d43jg1hdaf83fu ufrag=d43jg1hdaf83fu] ConnectivityCheckClient.startChecks#147: Start connectivity checks.
docker-jitsi-meet-jvb-1 | JVB 2023-10-21 20:16:03.473 INFO: [79] [confId=50ec61216d4a45e9 conf_name[email protected] meeting_id=8036ac00 epId=a9efe561 stats_id=Ezekiel-H3K] AllocationSettingsWrapper.setBandwidthAllocationSettings#174: Ignoring assumed-bandwidth-bps, not allowed in config.
docker-jitsi-meet-jicofo-1 | Jicofo 2023-10-21 20:16:05.031 INFO: [44] [room[email protected] meeting_id=8036ac00-542a-4b51-b238-281b2031c0fe participant=820c2b6e] Participant$JingleRequestHandlerImpl.onSessionOrTransportAccept#474: Received session-accept
docker-jitsi-meet-jicofo-1 | Jicofo 2023-10-21 20:16:05.032 INFO: [44] [room[email protected] meeting_id=8036ac00-542a-4b51-b238-281b2031c0fe] ColibriV2SessionManager.updateParticipant#548: Updating 820c2b6e with transport=org.jitsi.xmpp.extensions.jingle.IceUdpTransportPacketExtension@4c0bef5d, sources=[audio=[4289758838], video=[2663303376, 1911568358, 2833703446, 2688060195, 1273035399, 776020876], groups=[FID[2663303376, 1911568358], SIM[2663303376, 2833703446, 2688060195], FID[2833703446, 1273035399], FID[2688060195, 776020876]]]
docker-jitsi-meet-jicofo-1 | Jicofo 2023-10-21 20:16:05.033 INFO: [44] [room[email protected] meeting_id=8036ac00-542a-4b51-b238-281b2031c0fe] JitsiMeetConferenceImpl.acceptSession#1318: Accepted initial sources from 820c2b6e: [audio=[4289758838], video=[2663303376, 1911568358, 2833703446, 2688060195, 1273035399, 776020876], groups=[FID[2663303376, 1911568358], SIM[2663303376, 2833703446, 2688060195], FID[2833703446, 1273035399], FID[2688060195, 776020876]]]
docker-jitsi-meet-jicofo-1 | Jicofo 2023-10-21 20:16:05.036 INFO: [44] [room[email protected] meeting_id=8036ac00-542a-4b51-b238-281b2031c0fe participant=820c2b6e] Participant.sendQueuedRemoteSources#352: Sending a queued source-add, sources={a9efe561=[audio=[4136810578], video=[921552061, 2989166995], groups=[FID[921552061, 2989166995]]]}
docker-jitsi-meet-jicofo-1 | Jicofo 2023-10-21 20:16:05.036 INFO: [19] [room[email protected] meeting_id=8036ac00-542a-4b51-b238-281b2031c0fe participant=a9efe561] Participant.sendQueuedRemoteSources#352: Sending a queued source-add, sources={820c2b6e=[audio=[4289758838], video=[2663303376, 1911568358], groups=[FID[2663303376, 1911568358]]]}
docker-jitsi-meet-jvb-1 | JVB 2023-10-21 20:16:05.038 INFO: [79] [confId=50ec61216d4a45e9 conf_name[email protected] meeting_id=8036ac00 epId=820c2b6e stats_id=Velda-5V8] DtlsTransport.setSetupAttribute#126: The remote side is acting as DTLS client, we'll act as server
docker-jitsi-meet-jvb-1 | JVB 2023-10-21 20:16:05.039 INFO: [79] [confId=50ec61216d4a45e9 conf_name[email protected] meeting_id=8036ac00 epId=820c2b6e stats_id=Velda-5V8 local_ufrag=a3cko1hdaf83fc] IceTransport.startConnectivityEstablishment#204: Starting the Agent without remote candidates.
docker-jitsi-meet-jvb-1 | JVB 2023-10-21 20:16:05.039 INFO: [79] [confId=50ec61216d4a45e9 conf_name[email protected] meeting_id=8036ac00 epId=820c2b6e stats_id=Velda-5V8 local_ufrag=a3cko1hdaf83fc ufrag=a3cko1hdaf83fc] Agent.startConnectivityEstablishment#736: Start ICE connectivity establishment.
docker-jitsi-meet-jvb-1 | JVB 2023-10-21 20:16:05.040 INFO: [79] [confId=50ec61216d4a45e9 conf_name[email protected] meeting_id=8036ac00 epId=820c2b6e stats_id=Velda-5V8 local_ufrag=a3cko1hdaf83fc ufrag=a3cko1hdaf83fc] Agent.initCheckLists#972: Init checklist for stream stream-820c2b6e
docker-jitsi-meet-jvb-1 | JVB 2023-10-21 20:16:05.040 INFO: [79] [confId=50ec61216d4a45e9 conf_name[email protected] meeting_id=8036ac00 epId=820c2b6e stats_id=Velda-5V8 local_ufrag=a3cko1hdaf83fc ufrag=a3cko1hdaf83fc] Agent.setState#946: ICE state changed from Waiting to Running.
docker-jitsi-meet-jvb-1 | JVB 2023-10-21 20:16:05.041 INFO: [79] [confId=50ec61216d4a45e9 conf_name[email protected] meeting_id=8036ac00 epId=820c2b6e stats_id=Velda-5V8 local_ufrag=a3cko1hdaf83fc] IceTransport.iceStateChanged#347: ICE state changed old=Waiting new=Running
docker-jitsi-meet-jvb-1 | JVB 2023-10-21 20:16:05.041 INFO: [79] [confId=50ec61216d4a45e9 conf_name[email protected] meeting_id=8036ac00 epId=820c2b6e stats_id=Velda-5V8 local_ufrag=a3cko1hdaf83fc ufrag=a3cko1hdaf83fc] ConnectivityCheckClient.startChecks#147: Start connectivity checks.
docker-jitsi-meet-jvb-1 | JVB 2023-10-21 20:16:05.084 INFO: [79] [confId=50ec61216d4a45e9 conf_name[email protected] meeting_id=8036ac00 epId=820c2b6e stats_id=Velda-5V8] AllocationSettingsWrapper.setBandwidthAllocationSettings#174: Ignoring assumed-bandwidth-bps, not allowed in config.
docker-jitsi-meet-jicofo-1 | Jicofo 2023-10-21 20:16:05.160 INFO: [46] [room[email protected] meeting_id=8036ac00-542a-4b51-b238-281b2031c0fe] ColibriV2SessionManager.updateParticipant#548: Updating 820c2b6e with transport=null, sources=[audio=[4289758838], video=[2663303376, 1911568358, 2833703446, 2688060195, 1273035399, 776020876, 1038526, 1125964066, 1309271368, 1435316427, 2101950231, 2930369193], groups=[FID[2663303376, 1911568358], SIM[2663303376, 2833703446, 2688060195], FID[2833703446, 1273035399], FID[2688060195, 776020876], FID[1038526, 1435316427], SIM[1038526, 2101950231, 2930369193], FID[2101950231, 1125964066], FID[2930369193, 1309271368]]]
docker-jitsi-meet-jicofo-1 | Jicofo 2023-10-21 20:16:05.161 INFO: [14] [room[email protected] meeting_id=8036ac00-542a-4b51-b238-281b2031c0fe participant=a9efe561] Participant.sendQueuedRemoteSources#352: Sending a queued source-add, sources={820c2b6e=[audio=[], video=[1038526, 1435316427], groups=[FID[1038526, 1435316427]]]}
docker-jitsi-meet-web-1 | 68.93.137.145 - - [21/Oct/2023:20:16:05 -0500] "GET /xmpp-websocket?room=1st HTTP/2.0" 200 367 "https://video.munn.me/1st" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/118.0.0.0 Safari/537.36"
docker-jitsi-meet-jibri-1 | Jibri 2023-10-21 20:16:44.909 FINE: [20] WebhookClient$updateStatus$1.invokeSuspend#109: Updating 0 subscribers of status |
I fixed my issue with this by adding port forwarding between my docker host server and my VPS proxy, as well as changing some values in my .env file. Ubuntu Server Docker Host:
Ubuntu Server Proxy Host in the Cloud:
Also check to make sure you iptables docker chain include rules to allow such traffic:
.env file changes:
|
I use UFW, the ports are already openned but nothing works. How could you use the docker jvb ip if it changes everytime when the container restart? I just tried with the new jitsi version 9111 that says the went fixed the ws-colibri. But I have the same issue. |
On the server you have the Nginx-Proxy-Manager on; what does your PREROUTING iptable look like? The IP changing on the jvb doesn't matter if the routing is set up correctly. What does your ip route look like? |
Is the Jitsi server also the same VPS or on another server/container? If so, add that IP also to your JVB IP config as you did earlier.
|
@iarlemozaga
I downed all containers, did a docker-compose up -d again, and now it works? don't ask me! contact me personally if you wanna chat about it. |
In my setup I used nginx-rproxy in front of docker-jitsi-meet. I had the same issue like described in the title with every account using my jitsi instance, after updating from stable-8960-1 to stable-9111. The Console at the developer tools showed issues with colibri-ws. So I switched from using websockets to SCTP. This solved the issue, but few accounts were disconnected every few seconds. So I reactivated using websockets und disabled using sctp again and configured a websocket like described here but instead of addressing proxy_pass https://localhost:8443; I target http://jvb:9090, so I'm bypassing jitsi-meet-web and accessing jvb directly from the rproxy. Idea is taken from #1531. That also solved the issue described at the title. If it also solves the disconnecting of Chrome/Jitsi-Meet-Desktop-APPs will be shown tomorrow... |
Probably you could upgrade to stable-9111 and use the old regular expression |
I already did a fresh install with this new version 9111 and the same error persists |
What changes do you make in your deployment? How are you deploying this? Is there any proxy involved? |
For me, it always seems to work the first time I start the Docker containers. But when I shut down the containers and start them up again, I get exactly this error. Version: stable-9220-1 |
I'm using the same way since beginning Jitsi in docker version behing Nginx proxy manager (also docker) I already tried to add the nginx proxy manager network in the jitsi compose to make sure that they dont loose connection but nothing changes. I already tried rebooting machine, cleaning all volumes and settings but only jitsi dont work, the same Video Quality Impaired error persists and the connection stop immediatly when a 3rd person enter in the call. |
You can try accessing: https://meet.mozaga.org |
Are you adding rules or whatever is necessary to properly proxy the /colibri-ws route using WebSocket? |
on a custom setup, I have the same error message but screensharing/video/audio works normaly I did now set the environment Variable:JVB_ADVERTISED_IPS in the env that the videobridge runs in (?), assuming that is correct -> but that had no effect on the error message. |
Yes I did, and nothing changes, the same error persists. I also tried to use another domain to make sure that my domain dont affect but nothing changed again. |
I don't know if this is the same issue that people are having here, but adding |
I am seeing the same error, but my case is a little different than this. I am seeing the |
Check the JVB container logs, paste them here please. |
Getting the same errors. With two clients connected, after a while the UI says "Video Quality Impaired". When 3rd client connects it crashes for everyone. JVB container warning logs @saghul :
Javascript console log on FF 119.0.1 (64 bit):
Docker services:
|
Sorry we can't support custom setups. You are skipping a ton of env variables. |
@juhojama solved it by restarting turn server. |
Upgrade from stable-8960 to stable-9258 (stable-9220 gave same issues) Jitsi work with 2/3/4+ users, but I get po-pup as mentioned in Issue title and Console logs: BridgeChannel.js:91 WebSocket connection to 'wss://<jitsi_host_url>/colibri-ws/<jvb_IP>/6051a3d5c1b5fca4/cb639d46?pwd=43jir9t4rdo7ir2dmkd3s250bn' failed: JVB Logs Any advise? |
Note: stable-9078 works as expected |
The change from #1645 made it so that I had to set the Without this config change, it uses
All of my web calls go to This has fixed the issue where the Video Quality Impaired popup comes up over and over. |
I'm using nginx reverse proxy. I set COLIBRI_WEBSOCKET_REGEX env variable to the same value as my JVB_WS_SERVER_ID I also used NGINX to forward 10000 udp to the jvb VM I see in the websocket request (in the browser) the request is: wss://myservernamehere.com/colibri-ws/jvb/1658435c7.... (looks good) I'm still getting the "Video Quality Impared popup" Any other thoughts? |
@damionsteen the best thing to do is check the If that's working, you can then use |
Hi, JVB: Client: No i saw the last post of alexmars with the I then checked it by my self. In my I changed it to this, exec into the web-container and restarted the nginx webserver and it works now!
|
Hello, I'm using Jitsi Docker Version 8922
When its only 2 people connected it pops up everytime the message:
Video Quality Impaired - The bridge Channel has been disconnect
And when there are more than 2 people, the connection it pops up the same alert and everyone lost the video, screenshare and audio.
Does someone knows how to fix that? I already editted my .env added my domain, I'm also forwarding the ports
I've noticed a warning in the logs
docker-jitsi-meet-stable-8922-jvb-1: AllocationSettingsWrapper.setBandwidthAllocationSettings#174: Ignoring assumed-bandwidth-bps, not allowed in config.
Does someone had the same issue? I already tried to find something but no success
The text was updated successfully, but these errors were encountered: