lib-jitsi-meet
lib-jitsi-meet copied to clipboard
jitsi
Unable to join a room with latest build lib-jitsi-meet
Description
I cloned lib-jitsi-meet repo and ran npm install and npm run build with node version v16.15.0. I got a dist (umd + esm). I used the example from lib-jitsi-meet repo and replaced the lib-jitsi-meet script, with my own that i build before.
Current behavior
Getting error: Logger.js:154 2023-01-11T14:43:27.892Z [modules/xmpp/moderator.js] <Ir._handleError>: Failed to get a successful response, giving up. Error: Failed to get a successful response, giving up. at Ir._handleError (moderator.js:388:23) at Ir._handleIqError (moderator.js:437:10) at moderator.js:266:31 at P.Handler.handler (strophe.umd.js:2716:25) at P.Handler.run (strophe.umd.js:1875:33) at strophe.umd.js:3157:35 at Object.forEachChild (strophe.umd.js:830:21) at P.Connection._dataRecv (strophe.umd.js:3146:25) at N.Bosh._onRequestStateChange (strophe.umd.js:5012:19)
Expected Behavior
Should join room as expected.
Reproduce Error
See project in my repo: https://github.com/xXTraceXx/Jitsi-Error
Same here, on FreeBSD 13.2 and Jitsi Meet version 1.0.6991
Most probably you have a problem with the configuration. Not sure how you installed and configured, but have you configured the client proxy and updated its roster? https://github.com/jitsi/jitsi-meet/blob/609942654a3a892474f56b2e837ce3552092855a/debian/jitsi-meet-prosody.postinst#L213
Same here, on FreeBSD 13.2 and Jitsi Meet version 1.0.6991
Most probably you have a problem with the configuration. Not sure how you installed and configured, but have you configured the client proxy and updated its roster? https://github.com/jitsi/jitsi-meet/blob/609942654a3a892474f56b2e837ce3552092855a/debian/jitsi-meet-prosody.postinst#L213
You're most likely correct. When I made the previous post, there were still several details in my configs that were not yet right. While everything else may already be fixed, I think I have missed updating the roster. Will try that next.
For anyone reading this thread, a tip that may be useful: Don't assume that the problem is with jitsi-meet (Jitsi Meet, referring to the web user interface) until you have checked, double-checked and triple-checked that your Prosody vs. Jicofo vs. Jitsi-Videobridge configurations are "in sync" with each other.
It's also worth noting, that if you change jitsi-meet web user interface settings (in config.js), make sure you restart Nginx (just in case) and flush your browser cache (or restart the browser if debugging in private / incognito mode) to be 100% sure that you're not accidentally testing with old settings coming from a cache.
(How) Does this command get executed when using the upstream prosody docker image? We face the same errors, every 3rd or so connect to the k8s jitsi deployment fails with this error when the user is clicking "Join conference" and the error appears immediately.
