Installing jvb2 over a previous installation doesn’t remove the service file of jvb1 (which gets in the way when using autocompletion by pressing tab):
> systemctl status jitsi-videobridge
Loaded: masked (Reason: Unit jitsi-videobridge.service is masked.)
Active: inactive (dead)
Purging it shows me an error:
> sudo apt purge jitsi-videobridge
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
(Reading database ... 115686 files and directories currently installed.)
Purging configuration files for jitsi-videobridge (1126-1) ...
Removing user `jvb' ...
Warning: group `jitsi' has no more members.
userdel: user jvb is currently used by process 683
/usr/sbin/deluser: `/sbin/userdel jvb' returned error code 8. Exiting.
dpkg: error processing package jitsi-videobridge (--purge):
installed jitsi-videobridge package post-removal script subprocess returned error exit status 1
Errors were encountered while processing:
E: Sub-process /usr/bin/dpkg returned an error code (1)
And where can I find informations about the core features of jvb2? Don’t want to skim thousands of lines of very specific changlelog.
this didn’t worked for me.
Now i have not possibility to connect to anything.
After a second one joins, always “2020-04-02T07:17:02.947Z [conference.js] <X._onConferenceFailed>: CONFERENCE FAILED: conference.videobridgeNotAvailable” Reconnecting 20 secs …
Not possible to use it anymore. I also made Config fit to my needs again (yes with no syntax errors or something)
The next problem was that the videobridge could not connect to the xmpp server. The log showed:
org.jivesoftware.smack.sasl.SASLErrorException: SASLError using SCRAM-SHA-1: not-authorized
The solution was to edit /etc/jitsi/videobridge/sip-communicator.properties and change the password to the one of the jvb user that is stored in the prosody user database (SQL in my installation). (Related: https://github.com/jitsi/jitsi-meet/issues/5557)
All the issue we had seen the past week, including all those on Debian10 and those with wrong password for jvb, are considered fixed and are no in the unstable repo if anybody wants to try it out before we push them to stable. Thank you.
would work flawless, just remember to make a backup copy of your configurations in case you did something more than setting up the hostname and the certificate, since you’ll need to reconfigure those stuff
Well, if you setup by just making an apt install jitsi-meet it will configure by itself nginx, Java8 (i think, I’m not sure)
can you please elaborate about LDAP authentication for Jitsi Meet? I’d be very interested, but I found only a howto for implementing LDAP address book into Jitsi Desktop App.
Many thanks in advance,