Jitsi conferencing - rocket-chat-server 6.3.1

Description

I installed version 6.2.8 in July 2023 using snap on Ubuntu 20.04 on Oracle Cloud Infrastructure (kernel 5.15.0-1038-oracle). After that I enabled JITSI conferencing and started using the platform (just 5 users). Everything was working 100% until yesterday (August 25th, 2023). The problem is that JITSI started asking for a login (Google, Facebook or Git). I removed Jitsi and reinstalled but it did not help. I checked the server and saw that the platform got updated to 6.3.1. I tried to log in with Google but even so Jitsi fails.

I tired to udate with snap tp 6.3.2 but it seems not to be available yet.

I also installed with snap on a clean machine for testing (it installed 6.3.1) but the result is the same.

Is there some documentation to fix this problem? Is this a problem with version 6.3.1?

Server Setup Information

  • Version of Rocket.Chat Server: 6.3.1
  • Operating System: Ubuntu Linux 20.04
  • Deployment Method: snap
  • Number of Running Instances: 1
  • DB Replicaset Oplog:
  • NodeJS Version: installed with rocket chat snap
  • MongoDB Version: installed with rocket chat snap
  • Proxy: nginx
  • Firewalls involved: ufw (port 3000/tcp open everywhere)

Any additional Information

sudo snap services
Service Startup Current Notes
lxd.activate enabled inactive -
lxd.daemon enabled inactive socket-activated
oracle-cloud-agent.oracle-cloud-agent enabled active -
oracle-cloud-agent.oracle-cloud-agent-updater enabled active -
rocketchat-server.rocketchat-caddy disabled inactive -
rocketchat-server.rocketchat-mongo enabled active -
rocketchat-server.rocketchat-server enabled active -

sudo snap get rocketchat-server
Key Value
backup-on-refresh enable
ignore-errors false
mongo-oplog-url mongodb://localhost:27017/local
mongo-url mongodb://localhost:27017/parties
port 3000
siteurl http://my.rocket.chat.server:3000


Jitsi now require’s authentication:

I think the current work around would be be to host your own Jitsi instance and change the settings in the rocketchat app to use that instead, which is annoying as it is another system that you will need to maintain but is the only work around at the moment.

Thanks for your reply.