jitsi-meet: Updated debian-package (stable): Jitsi Meet stopped working

Hi there,

I just updated the packages.

apt-get update
apt-get dist-upgrade

jitsi-videobridge2 gets installed and jitsi-videobridge is removed. But after the upgrade nothing is working. With the Jitsi Meet Android app I can’t create or enter a conference. Same on desktop.

I then removed all packages and purged the config files: apt-get purgejitsi-meet jitsi-meet-web-config jitsi-meet-prosody jitsi-meet-turnserver jitsi-meet-web jicofo jitsi-videobridge2

Then I installed from scratch via quick-install. Still the same. Jitsi Meet stopped working.

Maybe a bug with the (new) package?

About this issue

Original URL
State: closed
Created 4 years ago
Comments: 49 (18 by maintainers)

Most upvoted comments

This asks for the FQDN and now also for a password,

I see, we now about this case, we saw sometimes on Debian re-ordering of the packages when installing them. I already have a fix for it in branch but didn’t have the time to test it on all operating systems and to create the PRs. Thanks for the detailed info, that helps a lot!

damencho on Apr 5, 2020

I solved it: apt-get remove ca-certificates-java coturn dnsutils java-common jicofo jitsi-meet jitsi-meet-prosody jitsi-meet-turnserver jitsi-meet-web jitsi-meet-web-config jitsi-videobridge2 libasound2 libasound2-data libavahi-client3 libavahi-common-data libavahi-common3 libcups2 libevent-2.1-6 libevent-core-2.1-6 libevent-extra-2.1-6 libevent-openssl-2.1-6 libevent-pthreads-2.1-6 libhiredis0.14 libirs161 liblcms2-2 libmariadb3 libnspr4 libnss3 libpcsclite1 libpq5 libxi6 libxrender1 libxtst6 lua-bitop lua-event lua-expat lua-filesystem lua-sec lua-socket lua5.2 mariadb-common mysql-common openjdk-11-jre-headless prosody sqlite3 ssl-cert uuid-runtime x11-common --purge

Then make a fresh install like: apt-get -y install jitsi-meet

I think one of the packages above leaves some information which conflicts with jvb2.

shellshocker on Mar 29, 2020

For me after upgrading the ubuntu packages yesterday (Mar 28th) a self signed certificate was in use instead of the Let’s Encrypt one. So I reissued it running the provided script /usr/share/jitsi-meet/scripts/install-letsencrypt-cert.sh and the old Let’s Encrypt cert from a few days ago was put in place again. Not sure, if this is the identical issue, that is described above, but I thought, I’d share my findings.

haslinger on Mar 29, 2020