Jicofo freezes at doStart() method

Recently I updated Jicofo to v706 (Remove OSGi, jitsi-desktop, libjitsi. (#683) · jitsi/jicofo@f168519 · GitHub)
It freezes at the doStart() method.
Can anyone help?

Jicofo 2021-01-24 22:57:53.024 INFO: [14] BaseBrewery.start#175: Joined brewery room: jibribrewery@internal.auth.xxxxx
Jicofo 2021-01-24 22:57:53.041 INFO: [14] BaseBrewery.start#175: Joined brewery room: jigasibreweryroom@internal.auth.xxxxx
Jicofo 2021-01-24 22:57:53.041 INFO: [14] XmppProtocolProvider.doConnect#217: XMPP provider connected (JID: focus@auth.xxxxx/focus)
Jicofo 2021-01-24 22:57:53.234 WARNING: [1] org.glassfish.jersey.server.wadl.WadlFeature.configure: JAXBContext implementation could not be found. WADL feature is disabled.
Jicofo 2021-01-24 22:57:53.323 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-24 22:57:53.561 INFO: [1] org.eclipse.jetty.server.handler.ContextHandler.doStart: Started o.e.j.s.ServletContextHandler@380e1909{/,null,AVAILABLE}
Jicofo 2021-01-24 22:57:53.574 INFO: [1] org.eclipse.jetty.server.AbstractConnector.doStart: Started ServerConnector@37ff4054{HTTP/1.1, (http/1.1)}{}
Jicofo 2021-01-24 22:57:53.575 INFO: [1] org.eclipse.jetty.server.Server.doStart: Started @2012ms

When I start a conference, it fails with the errors:

[JitsiMeetJS.js] <Object.getGlobalOnErrorHandler>:  UnhandledError: Focus error, retry after 2000 Script: null Line: null Column: null StackTrace:  Error: Focus error, retry after 200
CONFERENCE FAILED: conference.focusDisconnected

Fixed it by downgrading to v695.

you definitely should not upgrade to recent Jicofo without taking care of:

  • configuration
  • upgrading other components

There have been big internal changes.

I have considered both cases and still, Jicofo could not serve requests.

I’d say that the way to go is to examine traffic from jicofo to prosody, that’s exactly were most of the novelty is with recent jicofo and it could be where you’ll find why it does not work for you. For the record I have found a problem in the configuration parameter loading, I’m still investigating it.
Good luck.
Edit: the problem was only in debian packaging, if you are not using Debian it could NOT be that.