Connection failed using lib-jitsi-meet

I’m experimenting with a custom UI to connect to the server.
I use the lib-jitsi-meet API and it was working fine for a while (last checked on Tuesday).
But now I can no longer connect, I get the following error:

Logger.js:154 2019-11-22T11:07:45.952Z [modules/xmpp/xmpp.js] <t.value>:  (TIME) Strophe disconnected[item-not-found]:	 854.815000002418
Logger.js:154 2019-11-22T11:07:45.954Z [modules/statistics/statistics.js] <Function.S.sendAnalyticsAndLog>:  {"type":"operational","action":"connection.failed","attributes":{"error_type":"connection.otherError","error_message":"item-not-found","shard_changed":true,"suspend_time":0,"time_since_last_success":5}}
example.js:317 Connection Failed!

I’m using the example code in lib-jitsi-meet/tree/master/doc/example as a base, and I’ve copied the config values from the page. Copied them again today, to make sure the config values and lib-jitsi-meet version match up. But it still won’t work.

I’m trying to serve my files with a local https development server, but also made this JSitor snippet which shows the same behaviour:

Any help in fixing this issue would be greatly appreciated :slight_smile:

1 Like

I made another example but this time using

This is working, but using the non-beta example I posted above still causes “Connection Failed!”


Did you ever find a solution for the “production” servers? I have the same issue, “beta” works for me.


Hi rufovideo. Also for me it still works only with the “beta” server. Actually I gave up on building my app from scratch using lib-jitsi-meet. Instead I’m using the Jitsi Meet External API to embed the lovely Jitsi Meet UI in my Chrome extension. With the ‘basics’ covered thanks to the embedded Jitsi instance, I can focus on adding my extras. Since a Chrome extension has additional privileges (compared to regular web pages), I’m not limited to calling only the functions from the External API. I actually rely on calling some of the functions from lib-jitsi-meet, which is used ‘under the hood’ in the embedded Jitsi instance and exposed via APP.conference._room. When running your own Jitsi server, there’s no need to jump through these hoops. But this approach is the best I could come up with when using the official Jitsi servers. So if you’re making a Chrome extension, or an Electron app, this could be a possible solution.

1 Like

Thanks. I think I am going to proceed how you suggest.