Jitsi meet not working after Jicofo upgrade

Openfire Plugins openfire-meetings
1

Hello,

We had to upgrade Jitsi as latest version of Chrome doesn’t support plan B. I upgraded Jitsi meet to 6726 which resolved the issue with Chrome. Then, I upgraded Jicofo and JVB as well to 6726 which is causing following issue:

On starting conference, it keeps on reloading. I see this error in browser console:

lib-jitsi-meet.min.js?v=139:2 2022-01-11T15:27:20.034Z [JitsiMeetJS.js] <Object.getGlobalOnErrorHandler>: UnhandledError: Focus error, retry after 1000 Script: null Line: null Column: null StackTrace: Error: Focus error, retry after 1000
at Ls._allocateConferenceFocusError (.xyz Domain Names | Join Generation XYZ)
at .xyz Domain Names | Join Generation XYZ
at I.Handler.handler (.xyz Domain Names | Join Generation XYZ)
at I.Handler.run (.xyz Domain Names | Join Generation XYZ)
at .xyz Domain Names | Join Generation XYZ
at Object.forEachChild (.xyz Domain Names | Join Generation XYZ)
at I.Connection._dataRecv (.xyz Domain Names | Join Generation XYZ)
at M.Bosh._onRequestStateChange (.xyz Domain Names | Join Generation XYZ)
r @ lib-jitsi-meet.min.js?v=139:2
getGlobalOnErrorHandler @ lib-jitsi-meet.min.js?v=139:2

We are using Openfire server. After Jicofo upgrade, I noticed it is no longer available as component session

focus_component
focus_component1221×293 16 KB

I came across this change Remove the “focus” external component, use client_proxy instead. (#8381) · jitsi/jitsi-meet@b6f7f8f · GitHub
where focus is removed as external component.

It looks like jitsi meet is unable to communicate with jicofo.
Can any please advise how to get this working again?

Thanks!

2

See - https://github.com/igniterealtime/openfire-pade-plugin/issues/317

I suggest you use Pade plugin for openfire ver 1.5.2 - Ignite Realtime: Openfire Plugins

1 Like
3

Thanks @Dele_Olajide for the quick response.

I updated focus JID in config.js in jitsi meet and it resolved above issue.

However, I’m now seeing a different issue. I’m seeing only myself in the conference. When other participants try to join the conference, they see themselves. There is only one participant in the conference.

Here are the Jicofo logs.

2022-01-11 13:37:48.304 INFO: [263] ConferenceIqHandler.handleConferenceIq#65: Focus request for room: room12@conference.chat-app.domain.com
2022-01-11 13:37:48.304 INFO: [263] [room=room12@conference.chat-app.domain.com] JitsiMeetConferenceImpl.#264: Created new conference
2022-01-11 13:37:48.304 INFO: [263] [room=room12@conference.chat-app.domain.com] JitsiMeetConferenceImpl.joinTheRoom#446: Joining room12@conference.chat-app.domain.com
2022-01-11 13:38:07.125 INFO: [11] [room=room12@conference.chat-app.domain.com] JitsiMeetConferenceImpl.stop#423: Stopped.

Any ideas where to check?

I’ll check Pade plugin but we may be not able to install it immediately. Thanks

4

Jitsi Meet does not work out of the box with Openfire anymore because it has become more cloud focused and more dependent on Prosody server-side code developed in Lua like the client_proxy. You would need to port that code to Java and implement in an Openfire plugin as I did with Pade.
See - https://github.com/igniterealtime/openfire-pade-plugin/issues/358#issuecomment-894259196

After you get client_proxy working, you would need to hack app.bundle.min.js in order to overcome an incompatibility between Openfire and Prosody when focus is the only participant in a MUC room.

5

Thanks! It sound like a lot of work.

If we were to use Pade for Openfire, does it also allow to scale audio conferences out of box?

6

Not yet. It is work in progress. See - https://github.com/igniterealtime/openfire-pade-plugin/issues/376 and https://github.com/igniterealtime/openfire-pade-plugin/discussions/206

1 Like
7

This fix may fix the issue you have being the only one in a meeting that is cause when Openfire wrongly assumes a focus user is a ghost user.

1 Like
8

Is this change available in Openfire Release? To apply this change, do we need to update the Openfire source?