JVB fail after last upgrade

Ubuntu 18.04

Just upgraded Jitsi to latest through “apt-get upgrade”

after reboot, second user in conf would crash both users out of conf. (working install prior)

I then did the apt-get purge as instructed in the instruction on github. Had to manually kill prosody and turnserver.

reran apt-get purge just to be sure.

used the install command from the github instructions.

Same symptoms.
The following keeps repeating in jvb.log. System name was not changed

2020-05-09 17:56:10.794 INFO: [20] Videobridge.createConference#320: create_conf, id=42cbea5ed033a55b gid=null logging=false
2020-05-09 17:56:10.803 INFO: [20] AbstractHealthCheckService.run#171: Performed a successful health check in PT0.009S. Sticky failure: false
2020-05-09 17:56:11.123 INFO: [21] [hostname=localhost id=shard] MucClient.lambda$getConnectAndLoginCallable$7#648: Logging in.
2020-05-09 17:56:11.123 SEVERE: [21] RetryStrategy$TaskRunner.run#198: org.jivesoftware.smack.sasl.SASLErrorException: SASLError using SCRAM-SHA-1: not-authorized
org.jivesoftware.smack.sasl.SASLErrorException: SASLError using SCRAM-SHA-1: not-authorized
at org.jivesoftware.smack.SASLAuthentication.authenticationFailed(SASLAuthentication.java:292)
at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader.parsePackets(XMPPTCPConnection.java:1100)
at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader.access$300(XMPPTCPConnection.java:1000)
at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader$1.run(XMPPTCPConnection.java:1016)
at java.lang.Thread.run(Thread.java:748)
2020-05-09 17:56:16.125 INFO: [21] [hostname=localhost id=shard] MucClient.lambda$getConnectAndLoginCallable$7#648: Logging in.
2020-05-09 17:56:16.125 SEVERE: [21] RetryStrategy$TaskRunner.run#198: org.jivesoftware.smack.sasl.SASLErrorException: SASLError using SCRAM-SHA-1: not-authorized
org.jivesoftware.smack.sasl.SASLErrorException: SASLError using SCRAM-SHA-1: not-authorized
at org.jivesoftware.smack.SASLAuthentication.authenticationFailed(SASLAuthentication.java:292)
at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader.parsePackets(XMPPTCPConnection.java:1100)
at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader.access$300(XMPPTCPConnection.java:1000)
at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader$1.run(XMPPTCPConnection.java:1016)
at java.lang.Thread.run(Thread.java:748)
2020-05-09 17:56:20.794 INFO: [20] Videobridge.createConference#320: create_conf, id=2dd0f6c6a64b564b gid=null logging=false
2020-05-09 17:56:20.799 INFO: [20] AbstractHealthCheckService.run#171: Performed a successful health check in PT0.005S. Sticky failure: false
2020-05-09 17:56:21.126 INFO: [21] [hostname=localhost id=shard] MucClient.lambda$getConnectAndLoginCallable$7#648: Logging in.
2020-05-09 17:56:21.127 SEVERE: [21] RetryStrategy$TaskRunner.run#198: org.jivesoftware.smack.sasl.SASLErrorException: SASLError using SCRAM-SHA-1: not-authorized
org.jivesoftware.smack.sasl.SASLErrorException: SASLError using SCRAM-SHA-1: not-authorized
at org.jivesoftware.smack.SASLAuthentication.authenticationFailed(SASLAuthentication.java:292)
at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader.parsePackets(XMPPTCPConnection.java:1100)
at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader.access$300(XMPPTCPConnection.java:1000)
at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader$1.run(XMPPTCPConnection.java:1016)
at java.lang.Thread.run(Thread.java:748)
2020-05-09 17:56:26.128 INFO: [21] [hostname=localhost id=shard] MucClient.lambda$getConnectAndLoginCallable$7#648: Logging in.
2020-05-09 17:56:26.128 SEVERE: [21] RetryStrategy$TaskRunner.run#198: org.jivesoftware.smack.sasl.SASLErrorException: SASLError using SCRAM-SHA-1: not-authorized
org.jivesoftware.smack.sasl.SASLErrorException: SASLError using SCRAM-SHA-1: not-authorized
at org.jivesoftware.smack.SASLAuthentication.authenticationFailed(SASLAuthentication.java:292)
at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader.parsePackets(XMPPTCPConnection.java:1100)
at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader.access$300(XMPPTCPConnection.java:1000)
at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader$1.run(XMPPTCPConnection.java:1016)
at java.lang.Thread.run(Thread.java:748)

Do you know the previous version that was installed, and I suppose you updated from latest stable?

It would of been the “stable” from about 4 weeks ago (initial install). Updated from stable as per Ubuntu’s MOTD suggestion.

Was working fine. My experience with trying to fix other broken Jitsi installs is to wipe the OS and do a fresh install of both Ubuntu and Jitsi. I’ve never successfully uninstalled/reinstalled Jitsi and I end up spending hours chasing errors in log files and finding residual config data that should of been removed using purge.

Okay, now it’s worse.
I did a fresh install and update of Ubuntu 18.04
I did a line by line from the git instructions install of jitsi

Second user consistently crashes both users out of conference after briefly displaying both users.
Here are the versions it loaded:

jitsi/stable 2.10.5550-1 amd64
jitsi-archive-keyring/stable 1.0.1 all
jitsi-meet/stable,now 2.0.4548-1 all [installed]
jitsi-meet-prosody/stable,now 1.0.4074-1 all [installed,automatic]
jitsi-meet-tokens/stable 1.0.4074-1 all
jitsi-meet-turnserver/stable,now 1.0.4074-1 all [installed,automatic]
jitsi-meet-web/stable,now 1.0.4074-1 all [installed,automatic]
jitsi-meet-web-config/stable,now 1.0.4074-1 all [installed,automatic]
jitsi-upload-integrations/stable 0.13.13-1 all
jitsi-videobridge/stable 1126-1 amd64
jitsi-videobridge2/stable,now 2.1-197-g38256192-1 all [installed,automatic]