Can't create meeting room, keep reconnecting and showing focus error

Hello, I’ve just setup a new self-hosting Jitsi instance on Centos 7.9 and got problem when trying to create a meeting room on browser (I’ve never met on other instances before).

The console of Chrome seems showing problem relevant to focus component


Bosh request keeps return “Component unavailable”?!

The jicofo logs don’t point out anything except starting logs

Jicofo 2021-01-27 15:08:00.529 INFO: [1] JitsiConfig.<clinit>#47: Initialized newConfig: merge of system properties,reference.conf @ jar:file:/opt/jicofo/bin/jicofo.jar!/reference.conf: 1
Jicofo 2021-01-27 15:08:00.533 INFO: [1] ReadOnlyConfigurationService.reloadConfiguration#40: net.java.sip.communicator.SC_HOME_DIR_LOCATION not set
Jicofo 2021-01-27 15:08:00.534 INFO: [1] JitsiConfig.<clinit>#68: Initialized legacyConfig: sip communicator props (no description provided)
Jicofo 2021-01-27 15:08:00.534 INFO: [1] JitsiConfig$Companion.reloadNewConfig#94: Reloading the Typesafe config source (previously reloaded 0 times).
Jicofo 2021-01-27 15:08:00.881 INFO: [1] XmppServices.<init>#50: No dedicated Service XMPP connection configured, re-using the client XMPP connection.
Jicofo 2021-01-27 15:08:00.900 INFO: [1] BridgeSelector.<init>#77: Using org.jitsi.jicofo.bridge.SingleBridgeSelectionStrategy
Jicofo 2021-01-27 15:08:00.926 INFO: [1] JicofoServices.<init>#122: Starting FocusManager.
Jicofo 2021-01-27 15:08:00.927 WARNING: [1] FocusManager.start#134: Jicofo ID is not set correctly set (value=0). Configure a valid value [1-65535] by setting org.jitsi.jicofo.SHORT_ID in sip-communicator.properties or jicofo.octo.id in jicofo.conf. Future versions will require this for Octo.
Jicofo 2021-01-27 15:08:00.946 INFO: [1] JicofoServices.createAuthenticationAuthority#223: Authentication service disabled.
Jicofo 2021-01-27 15:08:00.952 INFO: [1] IqHandler.init#90: Registering IQ handlers with XmppConnection.
Jicofo 2021-01-27 15:08:00.954 INFO: [1] JicofoServices.<init>#165: Starting HTTP server with config: org.jitsi.rest.JettyBundleActivatorConfig@5c44c582.
Jicofo 2021-01-27 15:08:00.999 INFO: [1] org.eclipse.jetty.util.log.Log.initialized: Logging initialized @751ms to org.eclipse.jetty.util.log.Slf4jLog
Jicofo 2021-01-27 15:08:01.086 INFO: [1] org.eclipse.jetty.server.Server.doStart: jetty-9.4.35.v20201120; built: 2020-11-20T21:17:03.964Z; git: bdc54f03a5e0a7e280fab27f55c3c75ee8da89fb; jvm 1.8.0_282-b08
Jicofo 2021-01-27 15:08:01.227 INFO: [13] ProtocolProviderHandler.registrationChanged#94: ProtocolProviderHandler XmppClientConnectionConfig[hostname=localhost, port=5222, username=focus]: registered
Jicofo 2021-01-27 15:08:01.229 INFO: [13] IqHandler.init#90: Registering IQ handlers with XmppConnection.
Jicofo 2021-01-27 15:08:01.229 INFO: [13] ProtocolProviderHandler.registrationChanged#103: Set replyTimeout=PT15S
Jicofo 2021-01-27 15:08:01.230 INFO: [13] XmppProtocolProvider.doConnect#223: XMPP provider connected (JID: focus@auth.live.businessinformer.io/focus)
Jicofo 2021-01-27 15:08:01.443 WARNING: [1] org.glassfish.jersey.internal.inject.Providers.checkProviderRuntime: A provider org.jitsi.rest.Version registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider org.jitsi.rest.Version will be ignored.
Jicofo 2021-01-27 15:08:01.650 INFO: [1] org.eclipse.jetty.server.handler.ContextHandler.doStart: Started o.e.j.s.ServletContextHandler@3910fe11{/,null,AVAILABLE}
Jicofo 2021-01-27 15:08:01.661 INFO: [1] org.eclipse.jetty.server.AbstractConnector.doStart: Started ServerConnector@61e94def{HTTP/1.1, (http/1.1)}{0.0.0.0:8888}
Jicofo 2021-01-27 15:08:01.661 INFO: [1] org.eclipse.jetty.server.Server.doStart: Started @1414ms

The prosody logs keep warning “Component not connected” (debug level)

Jan 27 15:24:57 mod_bosh        debug   We have an open request, so sending on that
Jan 27 15:24:57 mod_bosh        debug   Request destroyed: table: 0x28de8f0
Jan 27 15:24:57 mod_bosh        debug   Session 56169ebf-d04b-44d4-aa89-24ec9a60b7b2 has 1 out of 1 requests open
Jan 27 15:24:57 mod_bosh        debug   and there are 0 things in the send_buffer:
Jan 27 15:24:57 mod_bosh        debug   Have nothing to say, so leaving request unanswered for now
Jan 27 15:25:00 http.server     debug   Firing event: POST /http-bind/
Jan 27 15:25:00 mod_bosh        debug   Handling new request table: 0x27a0060: <body rid="498617731" sid="56169ebf-d04b-44d4-aa89-24ec9a60b7b2" xmlns="http://jabber.org
/protocol/httpbind"><iq id="aee6fa9e-a1d9-4c46-9c6d-1ff566a78b18:sendIQ" to="focus.live.businessinformer.io" type="set" xmlns="jabber:client"><conference machine-uid="7
a10c0d82484ca265e369a01569ade58" room="bigdeparturesdisturbeffectively@conference.live.businessinformer.io" xmlns="http://jitsi.org/protocol/focus"><property name="disa
bleRtx" value="false"/></conference></iq></body>
----------
Jan 27 15:25:00 mod_bosh        debug   BOSH body open (sid: 56169ebf-d04b-44d4-aa89-24ec9a60b7b2)
Jan 27 15:25:00 bosh56169ebf-d04b-44d4-aa89-24ec9a60b7b2        debug   rid: 498617731, sess: 498617730, diff: 1
Jan 27 15:25:00 mod_bosh        debug   BOSH stanza received: <iq id='aee6fa9e-a1d9-4c46-9c6d-1ff566a78b18:sendIQ' type='set' to='focus.live.businessinformer.io'>

Jan 27 15:25:00 bosh56169ebf-d04b-44d4-aa89-24ec9a60b7b2        debug   Received[c2s]: <iq id='aee6fa9e-a1d9-4c46-9c6d-1ff566a78b18:sendIQ' type='set' to='focus.live.bu
sinessinformer.io'>
Jan 27 15:25:00 focus.live.businessinformer.io:component        warn    Component not connected, bouncing error for: <iq id='aee6fa9e-a1d9-4c46-9c6d-1ff566a78b18:sendIQ
' type='set' to='focus.live.businessinformer.io' from='uywpksjp-rgnce3u@live.businessinformer.io/-M6Bpw9U'>
Jan 27 15:25:00 mod_bosh        debug   We have an open request, so sending on that
Jan 27 15:25:00 mod_bosh        debug   Request destroyed: table: 0x2877240
Jan 27 15:25:00 mod_bosh        debug   Session 56169ebf-d04b-44d4-aa89-24ec9a60b7b2 has 1 out of 1 requests open
Jan 27 15:25:00 mod_bosh        debug   and there are 0 things in the send_buffer:
Jan 27 15:25:00 mod_bosh        debug   Have nothing to say, so leaving request unanswered for now
Jan 27 15:25:07 socket  debug   server.lua: accepted new client connection from ::1:53512 to 5280
Jan 27 15:25:07 http.server     debug   Firing event: POST /http-bind/
Jan 27 15:25:07 mod_bosh        debug   Handling new request table: 0x28cd280: <body rid="498617732" sid="56169ebf-d04b-44d4-aa89-24ec9a60b7b2" xmlns="http://jabber.org
/protocol/httpbind"><iq id="15847053-fb7a-47e9-acf0-0b81d429a244:sendIQ" to="focus.live.businessinformer.io" type="set" xmlns="jabber:client"><conference machine-uid="7a10c0d82484ca265e369a01569ade58" room="bigdeparturesdisturbeffectively@conference.live.businessinformer.io" xmlns="http://jitsi.org/protocol/focus"><property name="disableRtx" value="false"/></conference></iq></body>
----------
Jan 27 15:25:07 mod_bosh        debug   BOSH body open (sid: 56169ebf-d04b-44d4-aa89-24ec9a60b7b2)
Jan 27 15:25:07 bosh56169ebf-d04b-44d4-aa89-24ec9a60b7b2        debug   rid: 498617732, sess: 498617731, diff: 1
Jan 27 15:25:07 mod_bosh        debug   BOSH stanza received: <iq id='15847053-fb7a-47e9-acf0-0b81d429a244:sendIQ' type='set' to='focus.live.businessinformer.io'>

Jan 27 15:25:07 bosh56169ebf-d04b-44d4-aa89-24ec9a60b7b2        debug   Received[c2s]: <iq id='15847053-fb7a-47e9-acf0-0b81d429a244:sendIQ' type='set' to='focus.live.businessinformer.io'>
Jan 27 15:25:07 focus.live.businessinformer.io:component        warn    Component not connected, bouncing error for: <iq id='15847053-fb7a-47e9-acf0-0b81d429a244:sendIQ' type='set' to='focus.live.businessinformer.io' from='uywpksjp-rgnce3u@live.businessinformer.io/-M6Bpw9U'>

Somebody gives me a hint?

Yes, definitely focus/jicofo issue. Check the prosody config for the component “focus…”, check if you have a user “focus” for the “auth…” domain. On CentOS you maybe followed the manual installation, so some steps from the debian packages may be wrong or missing.

Here is the debian postinst, just for reference:

1 Like

Which version of jicofo is this?

The latest one (tag: jitsi-meet_5458), I cloned from the Github repo and built the package

This no longer uses component.
You need to configure that in prosody:

Component "focus.jitmeet.example.com" "client_proxy"
    target_address = "focusUser@auth.jitmeet.example.com"

This is handled by the debian packages automatically.

1 Like

Thank you @yasen @damencho

I updated the prosody config following your guide, so what jicofo starting command should be changed? I followed the instruction from GitHub - jitsi/jicofo: JItsi COnference FOcus is a server side focus component used in Jitsi Meet conferences., as below:

 ./jicofo.sh --domain=jitsi.exmaple.com --secret=focus_secret --user_domain=auth.jitsi.example.com --user_name=focus --user_password=focuspassword

Hi @vuhanguyen, did you resolve this error? if resolved, can u help me? thanks

Yes, I learnt how to create configs files by reading jitsi debian packages and docker source. Ping me on skype vu_ha_nguyen if you need some help.

@vuhanguyen it would be fantastic if you give a overview in a detailed post :heartbeat:

First, you need to change component like this

Component "focus.jitmeet.example.com" "client_proxy"
    target_address = "focusUser@auth.jitmeet.example.com"

“client_proxy” is important.

Second, you need to run this

prosodyctl mod_roster_command subscribe focus.$JVB_HOSTNAME $JICOFO_AUTH_USER@$JICOFO_AUTH_DOMAIN

Then stop prosody, jicofo, jvb and start them.

Can you please advise on the equivalent steps to be performed in Openfire to resolve focus component issue?

Thanks