Stopped working in FreeBSD

I have had Jitsi running on FreeBSD for a few about a year without problems. Recently after upgrading som packages it no longer works. In prosody logs I saw this message:
Jun 13 03:48:47 focus.xxxxxxxxxxxxxxx:component warn Component not connected, bouncing error for: <iq xml:lang='en' id='70efe1c9-62c4-4e40-9c6a-c47bc4d52b7f:sendIQ' type='set' to='focus.xxxxxxxxxxxxxxx' from='wtu6md0rtj4hzlkixvg1vu9w@xxxxxxxxxxxxxxx/yfLhcHO60sZG'>
Repeated a few times. Then, I followed some instructions here:

and after editing prosody configuration file for the domain and running prosodyctl mod_roster_command it no longer shows these messages in the log, but it still does not work. In browser log window I see for example this:
`Logger.js:154

   2022-06-13T02:16:20.387Z [modules/xmpp/moderator.js] <ar._allocateConferenceFocusError>:  Focus error, retry after 4000 <iq xmlns=​"jabber:​client" from=​"focus.xxxxxxxxxxxxxxx" to=​"tot-wrmkfy4uedner_yhhau4@xxxxxxxxxxxxxxx/​WjwJluzb3u7b" type=​"error" id=​"ff386c0a-d92b-4a92-bf5c-db64c1802560:​sendIQ">​…​</iq>​`

and also
`index.js:154

   2022-06-13T02:16:20.413Z [conference.js] <oce._onConferenceFailed>:  CONFERENCE FAILED: conference.focusDisconnected focus.xxxxxxxxxxxxxxx 4`

I assume I am missing some pieces here. What else do I need to reconfigure to make this work with latest versions of Jitsi related packages?

OS is FreeBSD 13.0.

Is this what you have for focus component in prosody config?

Yes, I changed it like that. Then I got messages instead about missing ‘/usr/local/lib/prosody/modules/share/lua/5.4/mod_client_proxy/mod_client_proxy.lua’. I also got similar messages first when I tried the prosodyctl mod_roster_command command line, but I found these modules in /usr/local/lib/prosody-modules so I made some symbolic links in the locations where prosody expected the module files which seemed to help at least for that particular problem.

Still not working in browsers or Jitsi app though.

Lua 5.4.2 and 5.2.4 are installed. Other package versions:
prosody-0.12.1
prosody-modules-20220319
jicofo-1.0.877
jitsi-meet-1.0.6155
jitsi-videobridge-2.1.681

Some more findings.
Tried to uninstall and reinstall prosody and prosody-modules and saw a note about adding plugin_paths = { "/usr/local/lib/prosody-modules" } to prosody.cfg.lua. When I did that, prosody finds modules without any need for links etc.

It feels like I am getting closer. It still does not work though and I am a bit lost now. I see nothing obvious in log files etc. This is about what prosody.log looks like after I try to connect:

Jun 15 05:17:02 startup info    Prosody is using the epoll backend for connection handling
Jun 15 05:17:02 portmanager     info    Activated service 'component' on [::1]:5347, [127.0.0.1]:5347
Jun 15 05:17:02 portmanager     info    Activated service 's2s' on [::]:5269, [*]:5269
Jun 15 05:17:02 portmanager     info    Activated service 's2s_direct_tls' on no ports
Jun 15 05:17:02 jitsi-videobridge.xxxxxxxxxxxxxxx:tls   info    Certificates loaded
Jun 15 05:17:02 portmanager     info    Activated service 'c2s' on [::]:5222, [*]:5222
Jun 15 05:17:02 portmanager     info    Activated service 'c2s_direct_tls' on no ports
Jun 15 05:17:02 portmanager     info    Activated service 'legacy_ssl' on no ports
Jun 15 05:17:02 portmanager     info    Activated service 'http' on [::1]:5280, [127.0.0.1]:5280
Jun 15 05:17:02 portmanager     info    Activated service 'https' on no ports
Jun 15 05:17:02 xxxxxxxxxxxxxxx:http    info    Serving 'bosh' at http://xxxxxxxxxxxxxxx:5280/http-bind
Jun 15 05:17:02 xxxxxxxxxxxxxxx:tls     info    Certificates loaded
Jun 15 05:17:02 auth.xxxxxxxxxxxxxxx:tls        info    Certificates loaded
Jun 15 05:17:02 conference.xxxxxxxxxxxxxxx:tls  info    Certificates loaded
Jun 15 05:17:02 focus.xxxxxxxxxxxxxxx:tls       info    Certificates loaded
Jun 15 05:17:02 mod_posix       info    Prosody is about to detach from the console, disabling further console output
Jun 15 05:17:02 mod_posix       info    Successfully daemonized to PID 21682
Jun 15 05:17:33 mod_bosh        info    New BOSH session, assigned it sid '1abbec22-6aa8-4a40-b388-e0b14254b247'
Jun 15 05:17:33 bosh1abbec22-6aa8-4a40-b388-e0b14254b247        info    Authenticated as -ow0_ziehtudny6fdb5bqrcf@xxxxxxxxxxxxxxx
Jun 15 05:17:47 bosh1abbec22-6aa8-4a40-b388-e0b14254b247        info    BOSH client disconnected: session close
Jun 15 05:17:48 mod_bosh        info    New BOSH session, assigned it sid '2b78556a-f125-4c5b-89d6-30b65f39fdb9'
Jun 15 05:17:48 bosh2b78556a-f125-4c5b-89d6-30b65f39fdb9        info    Authenticated as u38qcqs4lzhy4lxoruljs8gd@xxxxxxxxxxxxxxx
Jun 15 05:17:53 bosh2b78556a-f125-4c5b-89d6-30b65f39fdb9        info    BOSH client disconnected: session close```
(replaced actual domain name with xxxx)

Finally up and running again.

In case someone else is in the same situation:
I saw some hints in recent edits in this thread:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=257232

Apparently some other configuration files needed changes as well. I started over with sample config files for prosody, jvb and jicofo and modified to my domain settings etc and restarted and then all started working again!

1 Like