JITSI last release. Issues with JWT

Dear all, we have upgraded our jitsi server with the last release

Get:24 https://download.jitsi.org stable/ jitsi-videobridge2 2.2-45-ge8b20f06-1 [38.5 MB]
Get:25 https://download.jitsi.org stable/ jitsi-meet 2.0.7882-1 [3344 B]
Get:26 https://download.jitsi.org stable/ jicofo 1.0-940-1 [20.8 MB]
Get:27 https://download.jitsi.org stable/ jitsi-meet-web 1.0.6644-1 [16.4 MB]
Get:28 https://download.jitsi.org stable/ jitsi-meet-web-config 1.0.6644-1 [27.0 kB]
Get:29 https://download.jitsi.org stable/ jitsi-meet-prosody 1.0.6644-1 [67.3 kB]
Get:30 https://download.jitsi.org stable/ jitsi-meet-turnserver 1.0.6644-1 [5380 B]
Get:31 https://download.jitsi.org stable/ jitsi-meet-tokens 1.0.6644-1 [4040 B]

Currenlty we are running this:

jitsi (1.0.6260-1)
jitsi-meet (2.0.7439-1) …
jicofo (1.0-900-1) …
jitsi-videobridge2 (2.2-9-g8cded16e-1) …

With the last version, clients cannot connect using custom mobile app or the ufficial jitsi app.
Authentication is JWT based , this works with the “old” version but with the last version we cannot “access” the room: a loading image is showed and nobody cannot see the other participants

JVB 2022-11-04 09:40:29.954 INFO: [14] [hostname=localhost id=shard] MucClient.lambda$getConnectAndLoginCallable$9#638: Logging in.
JVB 2022-11-04 09:40:30.061 INFO: [14] [hostname=localhost id=shard] MucClient$2.authenticated#319: Authenticated, b=false
JVB 2022-11-04 09:40:30.136 INFO: [14] [hostname=localhost id=shard] MucClient$MucWrapper.join#763: Joined MUC: jvbbrewery@internal.auth.meet.x.com
JVB 2022-11-04 09:40:30.172 WARNING: [1] org.glassfish.jersey.server.wadl.WadlFeature.configure: JAXBContext implementation could not be found. WADL feature is disabled.
JVB 2022-11-04 09:40:30.286 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 2022-11-04 09:40:30.286 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 2022-11-04 09:40:30.287 WARNING: [1] org.glassfish.jersey.internal.inject.Providers.checkProviderRuntime: A provider org.jitsi.rest.prometheus.Prometheus 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.prometheus.Prometheus will be ignored.
JVB 2022-11-04 09:40:30.662 INFO: [1] org.eclipse.jetty.server.handler.ContextHandler.doStart: Started o.e.j.s.ServletContextHandler@2ff7a73{/,null,AVAILABLE}
JVB 2022-11-04 09:40:30.672 INFO: [1] org.eclipse.jetty.server.AbstractConnector.doStart: Started ServerConnector@62c5bbdc{HTTP/1.1, (http/1.1)}{127.0.0.1:8080}
JVB 2022-11-04 09:40:30.685 INFO: [1] org.eclipse.jetty.server.Server.doStart: Started Server@24528a25{STARTING}[11.0.10,sto=0] @3092ms

Jicofo 2022-11-04 09:43:31.481 INFO: [12] FocusManager$FocusExpireThread.expireLoop#403: Expiring JitsiMeetConferenceImpl[name=4577aa06-8c0b-467e-a45e-1497eb37f4ae@conference.meet.x.com]
Jicofo 2022-11-04 09:43:31.482 INFO: [12] [room=4577aa06-8c0b-467e-a45e-1497eb37f4ae@conference.meet.x.com meeting_id=fabed2f6-6e13-4662-8170-6d40e101650b] JitsiMeetConferenceImpl.stop#443:

We have rollbacked and noiw works again but we should upgrade the platform

Can you help me?

You may install the current stable Jitsi on a fresh box and apply your customizations to it manually.

What about “customization”?

The changes applied after the initial setup…
For example, enabling JWT athentication…