Joining a room shows an error page

Dear Jitsi folks,

After fixing the latest issues after upgrading – currently at jitsi-meet 2.0.6634-1 and jicofo 1.0-826-1 – there are no more SEVERE or ERROR lines in /var/log/jitsi/jicofo.log and /var/log/jitsi/jvb.log, but entering room and allowing access to the microphone the error page (Something went wrong) is shown. The browser console shows:

2021-11-23T16:36:20.147Z [JitsiMeetJS.js] <getGlobalOnErrorHandler>:  UnhandledError: Focus error, retry after 1000 Script: null Line: null Column: null StackTrace:  7273/Ns.prototype._allocateConferenceFocusError@https://jitsi.molgen.mpg.de/libs/lib-jitsi-meet.min.js?v=5586:2:381112
7273/Ns.prototype.allocateConferenceFocus/</<@https://jitsi.molgen.mpg.de/libs/lib-jitsi-meet.min.js?v=5586:2:380153
9230/sendIQ/a<@https://jitsi.molgen.mpg.de/libs/lib-jitsi-meet.min.js?v=5586:2:180542
run@https://jitsi.molgen.mpg.de/libs/lib-jitsi-meet.min.js?v=5586:2:175841
9230/_dataRecv/<@https://jitsi.molgen.mpg.de/libs/lib-jitsi-meet.min.js?v=5586:2:184279
forEachChild@https://jitsi.molgen.mpg.de/libs/lib-jitsi-meet.min.js?v=5586:2:167509
_dataRecv@https://jitsi.molgen.mpg.de/libs/lib-jitsi-meet.min.js?v=5586:2:184128
_onRequestStateChange@https://jitsi.molgen.mpg.de/libs/lib-jitsi-meet.min.js?v=5586:2:204112
EventHandlerNonNull*_newXHR@https://jitsi.molgen.mpg.de/libs/lib-jitsi-meet.min.js?v=5586:2:197935
9230/M.Request@https://jitsi.molgen.mpg.de/libs/lib-jitsi-meet.min.js?v=5586:2:196823
_onIdle@https://jitsi.molgen.mpg.de/libs/lib-jitsi-meet.min.js?v=5586:2:202586
_onIdle@https://jitsi.molgen.mpg.de/libs/lib-jitsi-meet.min.js?v=5586:2:192318
flush@https://jitsi.molgen.mpg.de/libs/lib-jitsi-meet.min.js?v=5586:2:179628
flush@https://jitsi.molgen.mpg.de/libs/lib-jitsi-meet.min.js?v=5586:2:364032
7273/Ns.prototype.allocateConferenceFocus/<@https://jitsi.molgen.mpg.de/libs/lib-jitsi-meet.min.js?v=5586:2:380206
7273/Ns.prototype.allocateConferenceFocus@https://jitsi.molgen.mpg.de/libs/lib-jitsi-meet.min.js?v=5586:2:379972
7273/join/<@https://jitsi.molgen.mpg.de/libs/lib-jitsi-meet.min.js?v=5586:2:385252
join@https://jitsi.molgen.mpg.de/libs/lib-jitsi-meet.min.js?v=5586:2:385091
7273/Oc.prototype.join@https://jitsi.molgen.mpg.de/libs/lib-jitsi-meet.min.js?v=5586:2:636680
connect@https://jitsi.molgen.mpg.de/libs/app.bundle.min.js?v=5586:138:186344
9932/startConference/<@https://jitsi.molgen.mpg.de/libs/app.bundle.min.js?v=5586:138:190019
startConference@https://jitsi.molgen.mpg.de/libs/app.bundle.min.js?v=5586:138:189985
init@https://jitsi.molgen.mpg.de/libs/app.bundle.min.js?v=5586:138:191115
async*9932/KL/</<@https://jitsi.molgen.mpg.de/libs/app.bundle.min.js?v=5586:136:24598
promise callback*9932/KL/<@https://jitsi.molgen.mpg.de/libs/app.bundle.min.js?v=5586:136:24573
1618/n/</</<@https://jitsi.molgen.mpg.de/libs/app.bundle.min.js?v=5586:138:1248248
9932/</</<@https://jitsi.molgen.mpg.de/libs/app.bundle.min.js?v=5586:138:391481
9932/</</<@https://jitsi.molgen.mpg.de/libs/app.bundle.min.js?v=5586:138:366055
9932/</</<@https://jitsi.molgen.mpg.de/libs/app.bundle.min.js?v=5586:138:365366
9932/</</<@https://jitsi.molgen.mpg.de/libs/app.bundle.min.js?v=5586:138:362741
9932/</</<@https://jitsi.molgen.mpg.de/libs/app.bundle.min.js?v=5586:138:362408
9932/</</<@https://jitsi.molgen.mpg.de/libs/app.bundle.min.js?v=5586:138:361800
9932/</</<@https://jitsi.molgen.mpg.de/libs/app.bundle.min.js?v=5586:138:359438
9932/</</<@https://jitsi.molgen.mpg.de/libs/app.bundle.min.js?v=5586:138:358577
9932/</</<@https://jitsi.molgen.mpg.de/libs/app.bundle.min.js?v=5586:138:356144
9932/</</<@https://jitsi.molgen.mpg.de/libs/app.bundle.min.js?v=5586:138:356067
9932/</</<@https://jitsi.molgen.mpg.de/libs/app.bundle.min.js?v=5586:138:341332
9932/</</<@https://jitsi.molgen.mpg.de/libs/app.bundle.min.js?v=5586:138:335006
9932/</</<@https://jitsi.molgen.mpg.de/libs/app.bundle.min.js?v=5586:138:334812
9932/</</<@https://jitsi.molgen.mpg.de/libs/app.bundle.min.js?v=5586:138:333824
9932/</</<@https://jitsi.molgen.mpg.de/libs/app.bundle.min.js?v=5586:138:329893
9932/</</<@https://jitsi.molgen.mpg.de/libs/app.bundle.min.js?v=5586:138:329016
9932/</</<@https://jitsi.molgen.mpg.de/libs/app.bundle.min.js?v=5586:138:327066
9932/</</<@https://jitsi.molgen.mpg.de/libs/app.bundle.min.js?v=5586:138:325720
9932/</</<@https://jitsi.molgen.mpg.de/libs/app.bundle.min.js?v=5586:138:325552
9932/</</<@https://jitsi.molgen.mpg.de/libs/app.bundle.min.js?v=5586:138:325410
9932/</</<@https://jitsi.molgen.mpg.de/libs/app.bundle.min.js?v=5586:138:324400
9932/</</<@https://jitsi.molgen.mpg.de/libs/app.bundle.min.js?v=5586:138:323992
9932/</</<@https://jitsi.molgen.mpg.de/libs/app.bundle.min.js?v=5586:138:321319
9932/</</<@https://jitsi.molgen.mpg.de/libs/app.bundle.min.js?v=5586:138:319231
9932/</</<@https://jitsi.molgen.mpg.de/libs/app.bundle.min.js?v=5586:138:318883
9932/</</<@https://jitsi.molgen.mpg.de/libs/app.bundle.min.js?v=5586:138:318601
9932/</</<@https://jitsi.molgen.mpg.de/libs/app.bundle.min.js?v=5586:138:318561
9932/</</<@https://jitsi.molgen.mpg.de/libs/app.bundle.min.js?v=5586:138:312989

When entering the room nothing is logged in the log files:

$ tail -f /var/log/jitsi/*log
==> /var/log/jitsi/jicofo.log <==
Jicofo 2021-11-23 17:34:34.111 INFO: [17] [type=bridge brewery=jvbbrewery] BaseBrewery.start#171: Joined the room.
Jicofo 2021-11-23 17:34:34.112 INFO: [17] [xmpp_connection=client] XmppProviderImpl.fireRegistrationStateChanged#331: Set replyTimeout=PT15S
Jicofo 2021-11-23 17:34:34.128 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-11-23 17:34:34.343 INFO: [1] org.eclipse.jetty.server.handler.ContextHandler.doStart: Started o.e.j.s.ServletContextHandler@f29353f{/,null,AVAILABLE}
Jicofo 2021-11-23 17:34:34.355 INFO: [1] org.eclipse.jetty.server.AbstractConnector.doStart: Started ServerConnector@1e6dad8{HTTP/1.1, (http/1.1)}{0.0.0.0:8888}
Jicofo 2021-11-23 17:34:34.355 INFO: [1] org.eclipse.jetty.server.Server.doStart: Started @2227ms
Jicofo 2021-11-23 17:34:38.727 INFO: [19] [type=bridge brewery=jvbbrewery] BaseBrewery.addInstance#341: Added brewery instance: jvbbrewery@internal.auth.jitsi.molgen.mpg.de/63b640cb-e1ed-4260-812f-15aca588faa2
Jicofo 2021-11-23 17:34:38.741 WARNING: [19] Main$1.warn#154: Key 'jicofo.bridge.average-participant-packet-rate-pps' from source 'typesafe config (reloaded 1 times)' is deprecated: use jicofo.bridge.average-participant-stress
Jicofo 2021-11-23 17:34:38.743 INFO: [19] BridgeSelector.addJvbAddress#125: Added new videobridge: Bridge[jid=jvbbrewery@internal.auth.jitsi.molgen.mpg.de/63b640cb-e1ed-4260-812f-15aca588faa2, relayId=null, region=null, stress=0.00]
Jicofo 2021-11-23 17:34:38.746 INFO: [19] JvbDoctor.addBridge#140: Scheduled health-check task for: jvbbrewery@internal.auth.jitsi.molgen.mpg.de/63b640cb-e1ed-4260-812f-15aca588faa2

==> /var/log/jitsi/jvb.log <==
JVB 2021-11-23 17:34:34.054 INFO: [20] [hostname=localhost id=shard] MucClient.lambda$getConnectAndLoginCallable$7#624: Logging in.
JVB 2021-11-23 17:34:34.162 INFO: [20] [hostname=localhost id=shard] MucClient$2.authenticated#307: Authenticated, b=false
JVB 2021-11-23 17:34:34.232 INFO: [20] [hostname=localhost id=shard] MucClient$MucWrapper.join#748: Joined MUC: jvbbrewery@internal.auth.jitsi.molgen.mpg.de
JVB 2021-11-23 17:34:34.326 WARNING: [1] org.glassfish.jersey.server.wadl.WadlFeature.configure: JAXBContext implementation could not be found. WADL feature is disabled.
JVB 2021-11-23 17:34:34.427 WARNING: [1] org.glassfish.jersey.internal.inject.Providers.checkProviderRuntime: A provider org.jitsi.rest.Health 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.Health will be ignored. 
JVB 2021-11-23 17:34:34.428 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. 
JVB 2021-11-23 17:34:34.738 INFO: [1] org.eclipse.jetty.server.handler.ContextHandler.doStart: Started o.e.j.s.ServletContextHandler@35a0e495{/,null,AVAILABLE}
JVB 2021-11-23 17:34:34.741 INFO: [1] org.eclipse.jetty.server.AbstractConnector.doStart: Started ServerConnector@75201592{HTTP/1.1, (http/1.1)}{127.0.0.1:8080}
JVB 2021-11-23 17:34:34.741 INFO: [1] org.eclipse.jetty.server.Server.doStart: Started @2475ms
JVB 2021-11-23 17:34:43.678 INFO: [25] HealthChecker.run#171: Performed a successful health check in PT0.00188S. Sticky failure: false

How can I debug this further?

Kind regards,

Paul

Share your prosody config, I suspect you are running with an old one without the client_proxy for the focus component.

Thank you for the quick reply. Unfortunately, I am not allowed to upload files. Therefore, pasted it to a Web service.

Which prosody version do you use? Check prosody for errors during an attempt or on restart.

I really wonder how your server ever worked with this configuration. When you see in the Jitsi doc something like

focusUser@auth…

this should NOT be taken litteraly, it’s assumed that you know that in fact the real name of the ‘focus’ (aka jicofo) is well, ‘focus’ and not ‘focusUser’. That’s coming from the idea that this user name could be a setup parameter, while I’m not sure at all that it’s possible now to change it (it’s hard coded in some Prosody modules). So replace focusUser by focus everywhere.

I am using prosody 0.11.2-1+deb10u2.

$ sudo journalctl -u prosody -b
-- Logs begin at Thu 2021-11-25 14:25:58 CET, end at Thu 2021-11-25 18:27:35 CET. --
Nov 25 14:25:58 jitsi systemd[1]: Started Prosody XMPP Server.
Nov 25 14:25:59 jitsi prosody[305]: portmanager: Error binding encrypted port for https: No certificate present in SSL/TLS configuration for https port 5281
Nov 25 14:25:59 jitsi prosody[305]: portmanager: Error binding encrypted port for https: No certificate present in SSL/TLS configuration for https port 5281

Thank you. As the Prosody configuration in /etc/prosody/conf.avail/jitsi.example.net.cfg.lua is not updated for all new features when using package upgrades, I took the template /usr/share/jitsi-meet-prosody/prosody.cfg.lua-jvb.example and incorrectly adapted it. Thank you for your observant eye. After doing the change, restarting Prosody and jicofo, the problem is solved.

Thank you very much.