Jitsi Meet keeps disconnecting after update

Hello,
We are deploying jitsi Meet on Kubernetes.
We had upgraded jitsi from version 4548-1 to version stable-5963 https://community.jitsi.org/t/multi-shard-auto-scalable-kubernetes-setup/64685. However, it keeps disconnecting.

Error logs from the web page:

[conference.js] <te._onConferenceFailed>:  CONFERENCE FAILED: conference.focusDisconnected focus.meet.jitsi

We already tried : https://community.jitsi.org/t/fixed-you-have-been-disconnected/21550/14

We added these env variables:

ENABLE_XMPP_WEBSOCKET = 0

and we added this configuration to the prosody configmap:

    Component "focus.{{ .Env.XMPP_DOMAIN }}" "client_proxy"
        target_address = "focus.{{ .Env.XMPP_AUTH_DOMAIN }}"

Logs from prosody:

conferenceduration.meet.jitsi:conference_duration_component  info	No muc component found, will listen for it: muc.meet.jitsi
conferenceduration.meet.jitsi:tls                            info	Certificates loaded
general                                                      info	Starting speakerstats for muc.meet.jitsi
speakerstats.meet.jitsi:speakerstats_component               info	No muc component found, will listen for it: muc.meet.jitsi
speakerstats.meet.jitsi:tls                                  info	Certificates loaded
focus.meet.jitsi:tls                                         info	Certificates loaded
auth.meet.jitsi:tls                                          info	Certificates loaded
muc.meet.jitsi:tls                                           info	Certificates loaded
muc.meet.jitsi:muc_domain_mapper                             info	Loading mod_muc_domain_mapper for host internal-muc.meet.jitsi!
muc.meet.jitsi:muc_domain_mapper                             info	Loading mod_muc_domain_mapper for host meet.jitsi!
muc.meet.jitsi:muc_domain_mapper                             info	Loading mod_muc_domain_mapper for host conferenceduration.meet.jitsi!
muc.meet.jitsi:muc_domain_mapper                             info	Loading mod_muc_domain_mapper for host speakerstats.meet.jitsi!
muc.meet.jitsi:muc_domain_mapper                             info	Loading mod_muc_domain_mapper for host auth.meet.jitsi!
muc.meet.jitsi:muc_domain_mapper                             info	Loading mod_muc_domain_mapper for host muc.meet.jitsi!
muc.meet.jitsi:muc_domain_mapper                             info	Loading mod_muc_domain_mapper for host focus.meet.jitsi!
conferenceduration.meet.jitsi:conference_duration_component  info	Hook to muc events on muc.meet.jitsi
speakerstats.meet.jitsi:speakerstats_component               info	Hook to muc events on muc.meet.jitsi
mod_bosh                                                     info	Client tried to use sid 'b4a10fb2-96b8-4570-8f31-cc5eb2e9e511' which we don't know about
mod_bosh                                                     info	Client tried to use sid 'b4a10fb2-96b8-4570-8f31-cc5eb2e9e511' which we don't know about
c2s5601fb3f6130                                              info	Client connected
c2s5601fb3f6130                                              info	Stream encrypted (TLSv1.2 with ECDHE-RSA-AES256-GCM-SHA384)
c2s5601fb3f6130                                              info	Authenticated as jvb@auth.meet.jitsi
mod_bosh                                                     info	Client tried to use sid '5b615afb-0756-46af-b87f-dc55b5a99759' which we don't know about
mod_bosh                                                     info	New BOSH session, assigned it sid '7f52c213-2bdb-4c88-8a9c-17e0f801e3d8'
bosh7f52c213-2bdb-4c88-8a9c-17e0f801e3d8                     info	Authenticated as w3vybprqoxocbpre@meet.jitsi
c2s5601fb480cb0                                              info	Client connected
c2s5601fb480cb0                                              info	Stream encrypted (TLSv1.2 with ECDHE-RSA-AES256-GCM-SHA384)
mod_bosh                                                     info	Client tried to use sid '5b615afb-0756-46af-b87f-dc55b5a99759' which we don't know about
c2s5601fb480cb0                                              info	Authenticated as focus@auth.meet.jitsi
mod_bosh                                                     info	New BOSH session, assigned it sid '260ef336-6f5b-4af0-8833-adeb62779b47'
bosh260ef336-6f5b-4af0-8833-adeb62779b47                     info	Authenticated as a-2h8qtlbdjqey9u@meet.jitsi
bosh7f52c213-2bdb-4c88-8a9c-17e0f801e3d8                     info	BOSH client disconnected: session close
bosh260ef336-6f5b-4af0-8833-adeb62779b47                     info	BOSH client disconnected: session close```
version stable 5076 doesn't work too.
All health checks are fine.

We had corrected the problem
Solution: https://community.jitsi.org/t/how-to-how-to-enable-websockets-xmpp-websocket-and-smacks-for-prosody/87920