Custom server connection failure
Closed this issue · 2 comments
I am using version 0.5.4 of the module, and I noticed a change in behaviour. My custom Jitsi server no longer works. I have rebooted the server. I have confirmed that it functions as a stand-alone service in a web browser. My credentials have not changed on the server, and I have not changed the firewall settings on either my Foundry server or Jitsi server.
I conducted this test with every other module disabled but the Jitsi module. My Jitsi server URL and credentials are set and verified. Custom URLs is selected in the module configuration settings.
The following errors appear in the log:
Logger.js:154 2021-04-04T20:06:02.108Z [modules/xmpp/strophe.util.js] <Object.r.Strophe.log>: Strophe: TypeError: this._jitsiConference.setReceiverConstraints is not a function
at JitsiRTCClient._onUserJoined (https:///modules/jitsirtc/scripts/jitsirtc.js:948:27)
at a.emit (https:///libs/lib-jitsi-meet.min.js:1:115270)
at ie.onMemberJoined (https:///libs/lib-jitsi-meet.min.js:10:56250)
at a.emit (https:///libs/lib-jitsi-meet.min.js:1:115213)
at E.onPresence (https:///libs/lib-jitsi-meet.min.js:10:155329)
at u.onPresence (https:///libs/lib-jitsi-meet.min.js:10:147587)
at I.Handler.run (https:///libs/lib-jitsi-meet.min.js:1:26549)
at https:///lib-jitsi-meet.min.js:1:34987
at Object.forEachChild (https:///libs/lib-jitsi-meet.min.js:1:18211)
at I.Connection._dataRecv (https:///libs/lib-jitsi-meet.min.js:1:34836)
at D.Bosh._onRequestStateChange (https:///libs/lib-jitsi-meet.min.js:1:54821)
Logger.js:154 2021-04-04T20:06:02.109Z [modules/xmpp/strophe.util.js] <Object.r.Strophe.log>: Strophe: error: this._jitsiConference.setReceiverConstraints is not a function
Logger.js:154 2021-04-04T20:09:14.780Z [modules/xmpp/strophe.ping.js] Ping timeout null
This is not the case when I select the public Jitsi server. That still works.
Also, awesome module. Thank you for building this. It has really improved gaming sessions with my friends during COVID.
Thank you for reporting this! It looks like older versions of Jitsi don't support a method I was using. This could probably have been fixed by upgrading Jitsi, but it may not be in the stable channel yet. The newly released v0.5.5 should no longer have this problem.
It works. Thanks!