Problem with users on chrome

Good morning,

As there was an issue with user in chrome I have upadate to the last version Jitsi-meet; actually as there was some conflits on the updeate I purge first:

sudo apt purge jigasi jitsi-meet jitsi-meet-web-config jitsi-meet-prosody jitsi-meet-turnserver jitsi-meet-web jicofo jitsi-videobridge2

and then:

sudo apt install jitsi-meet

But, after I did, “jitsi-meet is already the newest version (2.0.6826-1).” I am still having same issue with Chrome’s user…so only I get was disabling login to create rooms, which I will check later…

So if you have any suggestion, I would be more than welcome.

Thanks,

What problem exactly are you experiencing with Chrome? Can you gather and share browser js console logs from affected users?

Hi Freddie,

They have same issue they did before, let me explain:

User A- last Chrome version
User B- old Chrome version
User C-Firefox
User D-App

All them join a call, four user can see all are connected but user A see rest of them muted and camera off, and users B,C&D see user A muted and camera off. Users B,C&D can have no problems meeting. User A can see itself (camara and mic fine).

I have even tested in several pcs use an old chrome version, it works , when browser is upgrade stop working. Also in same pc works with edge or firefox and not with chrome.

Thanks,

Right, but you need to get some logs so we’re able to see what’s going on.
Can you test on meet.jit.si to see if you experience the same issue?

Hi,

On meet.jit.si works fine, it is on a ubuntu 18.04 server installation, this server was upgrade from 16.04. Issue is located on sever side but only affect chrome’s user.

Thanks

Ok. Gather the logs and share.

Some prosody stuff needs Ubuntu 20 Server in order to work, you won’t get the latest versions.

Hi,

I upgraded Prosody to last vesion before install Jitsi as guide said, I could upload sever but I would rather not but if it is the only option I will.

Thansk, I can see some errors but…

test:53 (TIME) index.html loaded: 845.4000000357628
Logger.js:154 2022-01-22T21:26:20.966Z [modules/browser/BrowserCapabilities.js] : This appears to be chrome, ver: 97.0.4692.99
LocalStatsCollector.js:22 The AudioContext was not allowed to start. It must be resumed (or created) after a user gesture on the page. Autoplay policy in Chrome - Chrome Developers
(anonymous) @ LocalStatsCollector.js:22
Logger.js:154 2022-01-22T21:26:21.077Z [modules/RTC/RTCUtils.js] list of media devices has changed: Array(5)
Logger.js:154 2022-01-22T21:26:21.680Z [features/base/redux] <Object.persistState>: redux state persisted. 00bb1cab8076923b74c56e45fbee4212 → 9cdbb9d4e638ab473f3b84076e50e8ec
Logger.js:154 2022-01-22T21:26:21.813Z [modules/statistics/AnalyticsAdapter.js] <Object.dispose>: Disposing of analytics adapter.
o @ Logger.js:154
Logger.js:154 2022-01-22T21:26:21.814Z [features/analytics] Initialized 0 analytics handlers
Logger.js:154 2022-01-22T21:26:21.816Z [features/base/media] Start muted:
Logger.js:154 2022-01-22T21:26:21.818Z [features/base/media] Start audio only set to false
Logger.js:154 2022-01-22T21:26:22.185Z [index.web] <HTMLDocument.>: (TIME) document ready: 2119.199999988079
olm.js:31 wasm streaming compile failed: TypeError: Failed to execute ‘compile’ on ‘WebAssembly’: Incorrect response MIME type. Expected ‘application/wasm’.
(anonymous) @ olm.js:31
olm.js:31 falling back to ArrayBuffer instantiation
(anonymous) @ olm.js:31
test:36 Service worker registered. ServiceWorkerRegistration
Logger.js:154 2022-01-22T21:26:22.674Z [modules/RTC/RTCUtils.js] Audio output device set to default
Logger.js:154 2022-01-22T21:26:22.794Z [modules/xmpp/xmpp.js] <I._initStrophePlugins>: P2P STUN servers: Array(1)
Logger.js:154 2022-01-22T21:26:22.856Z [modules/xmpp/xmpp.js] <I.connectionHandler>: (TIME) Strophe connecting: 2787.800000011921
Logger.js:154 2022-01-22T21:26:22.877Z [modules/RTC/RTCUtils.js] <Z.newObtainAudioAndVideoPermissions>: Using the new gUM flow
Logger.js:154 2022-01-22T21:26:22.881Z [modules/RTC/RTCUtils.js] <Z.>: Got media constraints: {“video”:{“height”:{“ideal”:720,“max”:720,“min”:240},“facingMode”:“user”},“audio”:{“optional”:[{},{“echoCancellation”:true},{“googEchoCancellation”:true},{“googAutoGainControl”:true},{“googNoiseSuppression”:true},{“googHighpassFilter”:true},{“googNoiseSuppression2”:true},{“googEchoCancellation2”:true},{“googAutoGainControl2”:true}]}}
lang/countries-enGB.json:1 Failed to load resource: the server responded with a status of 404 ()
Logger.js:154 2022-01-22T21:26:23.679Z [features/base/redux] <Object.persistState>: redux state persisted. 9cdbb9d4e638ab473f3b84076e50e8ec → 989f59d1f2e132b350ef18b2140c69f3
Logger.js:154 2022-01-22T21:26:24.105Z [modules/xmpp/XmppConnection.js] <u._maybeEnableStreamResume>: Stream resume enabled, but WebSockets are not enabled
o @ Logger.js:154
Logger.js:154 2022-01-22T21:26:24.105Z [modules/xmpp/strophe.ping.js] <d.startInterval>: XMPP pings will be sent every 10000 ms
Logger.js:154 2022-01-22T21:26:24.105Z [modules/xmpp/xmpp.js] <I.connectionHandler>: (TIME) Strophe connected: 4039.699999988079
Logger.js:154 2022-01-22T21:26:24.106Z [modules/xmpp/xmpp.js] <I.connectionHandler>: My Jabber ID: xbk06cwkqdb4lxpr@meet.test_com/lO28vUF1
Logger.js:154 2022-01-22T21:26:25.138Z [modules/RTC/RTCUtils.js] onUserMediaSuccess
Logger.js:154 2022-01-22T21:26:25.173Z [conference.js] <Object.startConference>: Initialized with 2 local tracks
Logger.js:154 2022-01-22T21:26:25.190Z [modules/xmpp/xmpp.js] <I.createRoom>: JID xbk06cwkqdb4lxpr@meet.test_com/lO28vUF1 using MUC nickname 77b99993
Logger.js:154 2022-01-22T21:26:25.194Z [modules/xmpp/ChatRoom.js] : Joined MUC as test@conference.meet.test_com/77b99993
Logger.js:154 2022-01-22T21:26:25.196Z [modules/e2eping/e2eping.js] : Initializing e2e ping; pingInterval=10000, analyticsInterval=60000.
Logger.js:154 2022-01-22T21:26:25.199Z [modules/connectivity/ParticipantConnectionStatus.js] : RtcMuteTimeout set to: 10000
Logger.js:154 2022-01-22T21:26:25.205Z [modules/statistics/AvgRTPStatsReporter.js] : Avg RTP stats will be calculated every 15 samples
Logger.js:154 2022-01-22T21:26:25.207Z [JitsiConference.js] : backToP2PDelay: 5
Logger.js:154 2022-01-22T21:26:25.210Z [JitsiConference.js] : End-to-End Encryprtion is supported
Logger.js:154 2022-01-22T21:26:25.349Z [JitsiConference.js] <ae._doReplaceTrack>: _doReplaceTrack - no JVB JingleSession
Logger.js:154 2022-01-22T21:26:25.351Z [JitsiConference.js] <ae._doReplaceTrack>: _doReplaceTrack - no P2P JingleSession
Logger.js:154 2022-01-22T21:26:25.362Z [JitsiConference.js] <ae._doReplaceTrack>: _doReplaceTrack - no JVB JingleSession
Logger.js:154 2022-01-22T21:26:25.362Z [JitsiConference.js] <ae._doReplaceTrack>: _doReplaceTrack - no P2P JingleSession
Logger.js:154 2022-01-22T21:26:25.365Z [modules/xmpp/moderator.js] <l.setFocusUserJid>: Focus jid set to: undefined
Logger.js:154 2022-01-22T21:26:25.368Z [modules/xmpp/moderator.js] <l.createConferenceIq>: Session ID: null machine UID: 167f22f6305eb80aae5ab7101e864101
Logger.js:154 2022-01-22T21:26:25.404Z [features/base/tracks] Replace audio track - unmuted
Logger.js:154 2022-01-22T21:26:25.408Z [features/base/tracks] Replace video track - unmuted
Logger.js:154 2022-01-22T21:26:25.606Z [modules/UI/videolayout/LargeVideoManager.js] hover in 77b99993
Logger.js:154 2022-01-22T21:26:25.627Z [modules/xmpp/moderator.js] <l.setFocusUserJid>: Focus jid set to: focus@auth.meet.test_com
Logger.js:154 2022-01-22T21:26:25.627Z [modules/xmpp/moderator.js] <l.parseConfigOptions>: Authentication enabled: false
Logger.js:154 2022-01-22T21:26:25.628Z [modules/xmpp/moderator.js] <l.parseConfigOptions>: External authentication enabled: false
Logger.js:154 2022-01-22T21:26:25.632Z [modules/xmpp/moderator.js] <l.parseConfigOptions>: Sip gateway enabled: false
index.js:9 wasm streaming compile failed: TypeError: Failed to execute ‘compile’ on ‘WebAssembly’: Incorrect response MIME type. Expected ‘application/wasm’.
(anonymous) @ index.js:9
index.js:9 falling back to ArrayBuffer instantiation
(anonymous) @ index.js:9
Logger.js:154 2022-01-22T21:26:25.898Z [modules/RTC/RTCUtils.js] <Z.newObtainAudioAndVideoPermissions>: Using the new gUM flow
Logger.js:154 2022-01-22T21:26:25.898Z [modules/RTC/RTCUtils.js] <Z.>: Got media constraints: {“video”:false,“audio”:{“optional”:[{“sourceId”:“default”},{“echoCancellation”:true},{“googEchoCancellation”:true},{“googAutoGainControl”:true},{“googNoiseSuppression”:true},{“googHighpassFilter”:true},{“googNoiseSuppression2”:true},{“googEchoCancellation2”:true},{“googAutoGainControl2”:true}]}}
Logger.js:154 2022-01-22T21:26:25.929Z [modules/xmpp/ChatRoom.js] <E.onPresence>: entered test@conference.meet.test_com/focus Object
Logger.js:154 2022-01-22T21:26:25.933Z [modules/version/ComponentsVersions.js] Got focus version: 1.0.840
Logger.js:154 2022-01-22T21:26:25.934Z [modules/xmpp/ChatRoom.js] <E.onPresence>: Jicofo supports restart by terminate: true
Logger.js:154 2022-01-22T21:26:25.937Z [modules/xmpp/ChatRoom.js] <E.onPresence>: entered test@conference.meet.test_com/a2060fb0 Object
Logger.js:154 2022-01-22T21:26:26.082Z [conference.js] <a.>: USER a2060fb0 connnected: a
Logger.js:154 2022-01-22T21:26:26.088Z [conference.js] <a.>: My role changed, new role: none
Logger.js:154 2022-01-22T21:26:26.106Z [modules/xmpp/ChatRoom.js] <E.onPresence>: (TIME) MUC joined: 6039.699999988079
Logger.js:154 2022-01-22T21:26:26.122Z [features/video-quality] : setReceiverVideoConstraint: 2160
Logger.js:154 2022-01-22T21:26:26.202Z [JitsiConference.js] <ae._maybeStartOrStopP2P>: Will start P2P with: test@conference.meet.test_com/a2060fb0
Logger.js:154 2022-01-22T21:26:26.207Z [JitsiConference.js] <ae._startP2PSession>: Created new P2P JingleSession test@conference.meet.test_com/77b99993 test@conference.meet.test_com/a2060fb0
Logger.js:154 2022-01-22T21:26:26.219Z [JitsiMeetJS.js] <Object.getGlobalOnErrorHandler>: UnhandledError: Strophe: Error: Failed to construct ‘RTCPeerConnection’: Plan B SDP semantics is a legacy version of the Session Description Protocol that has severe compatibility issues on modern browsers and is no longer supported. See https://www.chromestatus_com/feature/5823036655665152 for more details, including the possibility of registering for a Deprecation Trial in order to extend the Plan B deprecation deadline for a limited amount of time.
at new A (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:17:53903)
at A.createPeerConnection (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:1:106049)
at C.doInitialize (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:1:222580)
at C.initialize (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:17:12345)
at ae._startP2PSession (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:10:72844)
at ae._maybeStartOrStopP2P (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:10:74454)
at ae._onMucJoined (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:10:55334)
at a. (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:10:80758)
at a.emit (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:1:116111)
at E.onPresence (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:10:157370)
at u.onPresence (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:10:149744)
at I.Handler.run (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:1:26733)
at meetserversecure/libs/lib-jitsi-meet.min.js?v=139:1:35171
at Object.forEachChild (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:1:18395)
at I.Connection._dataRecv (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:1:35020)
at O.Bosh._onRequestStateChange (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:1:55005) Script: null Line: null Column: null StackTrace: Error: Strophe: Error: Failed to construct ‘RTCPeerConnection’: Plan B SDP semantics is a legacy version of the Session Description Protocol that has severe compatibility issues on modern browsers and is no longer supported. See https://www.chromestatus_com/feature/5823036655665152 for more details, including the possibility of registering for a Deprecation Trial in order to extend the Plan B deprecation deadline for a limited amount of time.
at new A (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:17:53903)
at A.createPeerConnection (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:1:106049)
at C.doInitialize (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:1:222580)
at C.initialize (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:17:12345)
at ae._startP2PSession (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:10:72844)
at ae._maybeStartOrStopP2P (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:10:74454)
at ae._onMucJoined (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:10:55334)
at a. (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:10:80758)
at a.emit (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:1:116111)
at E.onPresence (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:10:157370)
at u.onPresence (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:10:149744)
at I.Handler.run (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:1:26733)
at meetserversecure/libs/lib-jitsi-meet.min.js?v=139:1:35171
at Object.forEachChild (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:1:18395)
at I.Connection._dataRecv (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:1:35020)
at O.Bosh._onRequestStateChange (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:1:55005)
at Object.r.Strophe.log (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:17:16531)
at Object.fatal (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:1:23666)
at Object._handleError (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:1:23057)
at I.Handler.run (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:1:26761)
at meetserversecure/libs/lib-jitsi-meet.min.js?v=139:1:35171
at Object.forEachChild (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:1:18395)
at I.Connection._dataRecv (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:1:35020)
at O.Bosh._onRequestStateChange (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:1:55005)
o @ Logger.js:154
Logger.js:154 2022-01-22T21:26:26.220Z [modules/xmpp/strophe.util.js] <Object.r.Strophe.log>: Strophe: Error: Failed to construct ‘RTCPeerConnection’: Plan B SDP semantics is a legacy version of the Session Description Protocol that has severe compatibility issues on modern browsers and is no longer supported. See https://www.chromestatus_com/feature/5823036655665152 for more details, including the possibility of registering for a Deprecation Trial in order to extend the Plan B deprecation deadline for a limited amount of time.
at new A (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:17:53903)
at A.createPeerConnection (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:1:106049)
at C.doInitialize (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:1:222580)
at C.initialize (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:17:12345)
at ae._startP2PSession (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:10:72844)
at ae._maybeStartOrStopP2P (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:10:74454)
at ae._onMucJoined (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:10:55334)
at a. (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:10:80758)
at a.emit (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:1:116111)
at E.onPresence (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:10:157370)
at u.onPresence (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:10:149744)
at I.Handler.run (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:1:26733)
at meetserversecure/libs/lib-jitsi-meet.min.js?v=139:1:35171
at Object.forEachChild (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:1:18395)
at I.Connection._dataRecv (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:1:35020)
at O.Bosh._onRequestStateChange (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:1:55005)
o @ Logger.js:154
Logger.js:154 2022-01-22T21:26:26.221Z [JitsiMeetJS.js] <Object.getGlobalOnErrorHandler>: UnhandledError: Strophe: error: Failed to construct ‘RTCPeerConnection’: Plan B SDP semantics is a legacy version of the Session Description Protocol that has severe compatibility issues on modern browsers and is no longer supported. See https://www.chromestatus_com/feature/5823036655665152 for more details, including the possibility of registering for a Deprecation Trial in order to extend the Plan B deprecation deadline for a limited amount of time. Script: null Line: null Column: null StackTrace: Error: Strophe: error: Failed to construct ‘RTCPeerConnection’: Plan B SDP semantics is a legacy version of the Session Description Protocol that has severe compatibility issues on modern browsers and is no longer supported. See https://www.chromestatus_com/feature/5823036655665152 for more details, including the possibility of registering for a Deprecation Trial in order to extend the Plan B deprecation deadline for a limited amount of time.
at Object.r.Strophe.log (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:17:16531)
at Object.fatal (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:1:23666)
at Object._handleError (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:1:23276)
at I.Handler.run (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:1:26761)
at meetserversecure/libs/lib-jitsi-meet.min.js?v=139:1:35171
at Object.forEachChild (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:1:18395)
at I.Connection._dataRecv (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:1:35020)
at O.Bosh._onRequestStateChange (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:1:55005)
o @ Logger.js:154
Logger.js:154 2022-01-22T21:26:26.222Z [modules/xmpp/strophe.util.js] <Object.r.Strophe.log>: Strophe: error: Failed to construct ‘RTCPeerConnection’: Plan B SDP semantics is a legacy version of the Session Description Protocol that has severe compatibility issues on modern browsers and is no longer supported. See https://www.chromestatus_com/feature/5823036655665152 for more details, including the possibility of registering for a Deprecation Trial in order to extend the Plan B deprecation deadline for a limited amount of time.
o @ Logger.js:154
Logger.js:154 2022-01-22T21:26:26.222Z [modules/xmpp/strophe.util.js] <Object.r.Strophe.log>: Strophe: Removing Strophe handlers due to uncaught exception: Failed to construct ‘RTCPeerConnection’: Plan B SDP semantics is a legacy version of the Session Description Protocol that has severe compatibility issues on modern browsers and is no longer supported. See https://www.chromestatus_com/feature/5823036655665152 for more details, including the possibility of registering for a Deprecation Trial in order to extend the Plan B deprecation deadline for a limited amount of time.
o @ Logger.js:154
Logger.js:154 2022-01-22T21:26:26.238Z [modules/xmpp/ChatRoom.js] <E.onMessage>: Subject is changed to
Logger.js:154 2022-01-22T21:26:26.441Z [modules/RTC/RTCUtils.js] onUserMediaSuccess
TrackVADEmitter.js:112 [Deprecation] The ScriptProcessorNode is deprecated. Use AudioWorkletNode instead. (Enter Audio Worklet  |  Web  |  Google Developers)
_initializeAudioContext @ TrackVADEmitter.js:112
Logger.js:154 2022-01-22T21:26:26.556Z [modules/xmpp/strophe.jingle.js] <g.onJingle>: on jingle session-initiate from test@conference.meetsever/focus <iq xmlns=​"jabber:​client" type=​"set" to=​"xbk06cwkqdb4lxpr@meetsever/​lO28vUF1" from=​"test@conference.meetsever/​focus" id=​"eGJrMDZjd2txZGI0bHhwckBtZWV0LmFmcy1zZXJ2aWNlcy5jb20vbE8yOHZVRjEAN0w5MUMtOTczMgCaMzBG9+H5IMd7Tr0yHdDF">​…​​
Logger.js:154 2022-01-22T21:26:26.557Z [modules/xmpp/strophe.jingle.js] <g.onJingle>: (TIME) received session-initiate: 6490.699999988079
Logger.js:154 2022-01-22T21:26:26.557Z [modules/xmpp/strophe.jingle.js] <g.onJingle>: Marking session from test@conference.meetsever/focus as not P2P
Logger.js:154 2022-01-22T21:26:26.564Z [JitsiMeetJS.js] <Object.getGlobalOnErrorHandler>: UnhandledError: Failed to construct ‘RTCPeerConnection’: Plan B SDP semantics is a legacy version of the Session Description Protocol that has severe compatibility issues on modern browsers and is no longer supported. See https://www.chromestatus_com/feature/5823036655665152 for more details, including the possibility of registering for a Deprecation Trial in order to extend the Plan B deprecation deadline for a limited amount of time. Script: null Line: null Column: null StackTrace: Error: Failed to construct ‘RTCPeerConnection’: Plan B SDP semantics is a legacy version of the Session Description Protocol that has severe compatibility issues on modern browsers and is no longer supported. See https://www.chromestatus_com/feature/5823036655665152 for more details, including the possibility of registering for a Deprecation Trial in order to extend the Plan B deprecation deadline for a limited amount of time.
at new A (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:17:53903)
at A.createPeerConnection (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:1:106049)
at C.doInitialize (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:1:222580)
at C.initialize (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:17:12345)
at ae._acceptJvbIncomingCall (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:10:59848)
at ae.onIncomingCall (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:10:59349)
at a.emit (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:1:116054)
at g.onJingle (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:10:211302)
at I.Handler.run (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:1:26733)
at meetserversecure/libs/lib-jitsi-meet.min.js?v=139:1:35171
at Object.forEachChild (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:1:18395)
at I.Connection._dataRecv (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:1:35020)
at O.Bosh._onRequestStateChange (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:1:55005)
o @ Logger.js:154
Logger.js:154 2022-01-22T21:26:26.564Z [JitsiConference.js] <ae._acceptJvbIncomingCall>: DOMException: Failed to construct ‘RTCPeerConnection’: Plan B SDP semantics is a legacy version of the Session Description Protocol that has severe compatibility issues on modern browsers and is no longer supported. See https://www.chromestatus_com/feature/5823036655665152 for more details, including the possibility of registering for a Deprecation Trial in order to extend the Plan B deprecation deadline for a limited amount of time.
at new A (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:17:53903)
at A.createPeerConnection (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:1:106049)
at C.doInitialize (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:1:222580)
at C.initialize (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:17:12345)
at ae._acceptJvbIncomingCall (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:10:59848)
at ae.onIncomingCall (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:10:59349)
at a.emit (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:1:116054)
at g.onJingle (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:10:211302)
at I.Handler.run (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:1:26733)
at meetserversecure/libs/lib-jitsi-meet.min.js?v=139:1:35171
at Object.forEachChild (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:1:18395)
at I.Connection._dataRecv (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:1:35020)
at O.Bosh._onRequestStateChange (meetserversecure/libs/lib-jitsi-meet.min.js?v=139:1:55005)
o @ Logger.js:154
Logger.js:154 2022-01-22T21:26:26.612Z [modules/UI/videolayout/LargeVideoManager.js] hover in a2060fb0
Logger.js:154 2022-01-22T21:26:36.086Z [JitsiConference.js] <u.sendMessage>: Failed to send E2E ping request or response. undefined
o @ Logger.js:154
(anonymous) @ JitsiConference.js:376
sendRequest @ e2eping.js:93
Logger.js:154 2022-01-22T21:26:45.940Z [JitsiConference.js] <u.sendMessage>: Failed to send E2E ping request or response. undefined
o @ Logger.js:154
(anonymous) @ JitsiConference.js:376
sendRequest @ e2eping.js:93

Paste the output of this command:

dpkg -l | grep jitsi

dpkg -l | grep jitsi
ii jitsi-meet 2.0.6826-1 all WebRTC JavaScript video conferences
ii jitsi-meet-prosody 1.0.5764-1 all Prosody configuration for Jitsi Meet
ii jitsi-meet-turnserver 1.0.5764-1 all Configures coturn to be used with Jitsi Meet
ii jitsi-meet-web 1.0.5764-1 all WebRTC JavaScript video conferences
ii jitsi-meet-web-config 1.0.5764-1 all Configuration for web serving of Jitsi Meet
ii jitsi-videobridge2 2.1-607-g153f7e4e-1 all WebRTC compatible Selective Forwarding Unit (SFU)

Something is definitely wrong with your server. Perhaps you have some old configs left that are conflicting but what you’re reporting from grep and what your browser logs are showing don’t match. The logs show your deployment is still trying to negotiate Plan B, which shouldn’t be if you’re truly running v6826-1.

To save yourself this perpetual hassle, I’d recommend at this point that you update your OS to 20.04 and then reinstall Jitsi. Otherwise, you’re likely to run into other issues even if we’re able to get to the bottom of the current one.

Thanks Freddie, what do you think it should be the best way to proceed?
Shall I purge as I did before and delete all files related (which folders shall I delete?) and then upgrade to 20.04? a purge and upgrade? or directly upgradre to 20.04 would be enought?

Thanks again,

I’d say purge, then upgrade to 20.04. After that, reinstall Jitsi.

1 Like

Thanks, I will do and let you know :slight_smile:

I did and still the same :frowning:

Just I think if I should remove something manually…web interface is same I had before purge…if you could oriented me I would really appreciate it

Is your server bare metal or cloud hosted?

it is cloud hosted

In that case, can you not just get rid of the instance and start with a fresh instance?

sorry I really did not express well my selft. It is VM hosted in cloud, a practical effects it a bare metal server.

Oh ok. Well, can you get a fresh VM? That way you can start from scratch - get OS (Ubuntu 20.04 LTS), then install Jitsi.