New participant kicks first participant, strange connection error in jvb.log

Hello all,
Standard installation with quick install guide on Debian Buster, behind NAT, Advanced configuration has been done.
As soon as a new user enters the chat room, the first user is dropped.
After a restart of jitsi-videobridge this error occurs:

JVB 2020-03-31 21:00:06.502 INFORMATION: [17] org.jitsi.xmpp.mucclient.MucClientManager.log() Setting a presence extension: org.jitsi.xmpp.extensions.colibr$
JVB 2020-03-31 21:00:06.579 INFORMATION: [22] org.jitsi.videobridge.health.Health.log() Performed a successful health check in 1031ms. Sticky failure: false
JVB 2020-03-31 21:00:06.583 WARNUNG: [58] org.ice4j.ice.Agent.log() Agent contains no IceMediaStream with name stream!
JVB 2020-03-31 21:00:06.587 WARNUNG: [59] org.ice4j.ice.Agent.log() Agent contains no IceMediaStream with name stream!
JVB 2020-03-31 21:00:06.878 INFORMATION: [30] org.jitsi.xmpp.mucclient.MucClient.log() [MucClient id=shard hostname=localhost] connected
JVB 2020-03-31 21:00:06.923 SCHWERWIEGEND: [30] org.jitsi.xmpp.mucclient.MucClientManager.log() Failed to initialize and start a MucClient:
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.base/java.lang.Thread.run(Thread.java:834)

Thank you for your input in times of much needed webconferences!
Best,
Tobias

This is jvb using wrong password when connecting to the xmpp server. We discovered a bug where some data is left on uninstall that can lead to this.
Here is one workaround SASLError using SCRAM-SHA-1: not-authorized - on Debian buster system with existing prosody

Thank you so much!
Indeed, this solved the problem.
Another Jitsi Server easing the problems of quarantine!

Ok, I was happy to early,
I changed the settings to allow only registered users to open new chat rooms and now I do not have audio or video any more. Even as I undo my changes (I followed the instructions to the letter) It still does not show audio and video. I am getting this errors in the browser console:
ICE failed, add a STUN server and see about:webrtc for more details
2020-04-01T17:42:08.062Z [modules/RTC/BridgeChannel.js] : Bridge Channel send: no opened channel.

I invested now 10+ hours in getting the quick start running… this is a little bit frustrating.

Ok, a quick check showed, that it works in Chrome but not in Firefox…
Is there a special config to be made, and why did it work the first time in Firefox, but now not anymore?
Questions over Questions…

Also if three chromes connect, one is dropped.

Check js console logs, what error do you see? Probably no jvb instances, then check jvb logs.

After the third participant joins:

Logger.js:154 2020-04-01T20:54:31.408Z [JitsiConference.js] <e.sendMessage>:  Failed to send E2E ping request or response. undefined
o @ Logger.js:154
(anonymous) @ JitsiConference.js:337
value @ e2eping.js:92
Logger.js:154 2020-04-01T20:54:31.756Z [modules/RTC/BridgeChannel.js] <e.value>:  Bridge Channel send: no opened channel.
o @ Logger.js:154
value @ BridgeChannel.js:395
value @ BridgeChannel.js:189
value @ RTC.js:908
oe.sendEndpointMessage @ JitsiConference.js:2454
oe.broadcastEndpointMessage @ JitsiConference.js:2464
value @ ConnectionQuality.js:461
value @ ConnectionQuality.js:532
c.emit @ events.js:151
f._processAndEmitReport @ RTPStatsCollector.js:827
f.processStatsReport @ RTPStatsCollector.js:701
(anonymous) @ RTPStatsCollector.js:341
Logger.js:154 2020-04-01T20:54:36.023Z [modules/RTC/BridgeChannel.js] <e.value>:  Bridge Channel send: no opened channel.
o @ Logger.js:154
value @ BridgeChannel.js:395
value @ BridgeChannel.js:189
value @ RTC.js:908
oe.sendEndpointMessage @ JitsiConference.js:2454
oe.sendMessage @ JitsiConference.js:2498
(anonymous) @ JitsiConference.js:334
value @ e2eping.js:92
Logger.js:154 2020-04-01T20:54:36.023Z [JitsiConference.js] <e.sendMessage>:  Failed to send E2E ping request or response. undefined
o @ Logger.js:154
(anonymous) @ JitsiConference.js:337
value @ e2eping.js:92

No Errors in the jvb.log, only some Warnings:

2020-04-01 22:58:26.313 WARNUNG: [1098] [confId=8b6266a6a8e5656e epId=5750f493 gid=ffea4d stats_id=Zula-fcG conf_name=ivan] AbstractEndpointMessageTransport.onClientEndpointMessage#219: Unable to find endpoint 88e0378a to send EndpointMessage
2020-04-01 22:58:32.696 WARNUNG: [1194] [confId=8b6266a6a8e5656e epId=29372863 gid=ffea4d stats_id=Gwendolyn-5dJ conf_name=ivan] AbstractEndpointMessageTransport.onClientEndpointMessage#219: Unable to find endpoint 88e0378a to send EndpointMessage
2020-04-01 22:58:41.874 WARNUNG: [1194] [confId=8b6266a6a8e5656e epId=29372863 gid=ffea4d stats_id=Gwendolyn-5dJ conf_name=ivan] AbstractEndpointMessageTransport.onClientEndpointMessage#219: Unable to find endpoint 88e0378a to send EndpointMessage
2020-04-01 22:58:44.788 WARNUNG: [1177] [confId=8b6266a6a8e5656e epId=29372863 gid=ffea4d stats_id=Gwendolyn-5dJ conf_name=ivan] AbstractEndpointMessageTransport.onClientEndpointMessage#219: Unable to find endpoint e4349b15 to send EndpointMessage
2020-04-01 22:58:51.870 WARNUNG: [1194] [confId=8b6266a6a8e5656e epId=29372863 gid=ffea4d stats_id=Gwendolyn-5dJ conf_name=ivan] AbstractEndpointMessageTransport.onClientEndpointMessage#219: Unable to find endpoint 88e0378a to send EndpointMessage
2020-04-01 22:59:01.901 WARNUNG: [1177] [confId=8b6266a6a8e5656e epId=29372863 gid=ffea4d stats_id=Gwendolyn-5dJ conf_name=ivan] AbstractEndpointMessageTransport.onClientEndpointMessage#219: Unable to find endpoint 88e0378a to send EndpointMessage
2020-04-01 22:59:11.876 WARNUNG: [1177] [confId=8b6266a6a8e5656e epId=29372863 gid=ffea4d stats_id=Gwendolyn-5dJ conf_name=ivan] AbstractEndpointMessageTransport.onClientEndpointMessage#219: Unable to find endpoint 88e0378a to send EndpointMessage
2020-04-01 22:59:21.871 WARNUNG: [1194] [confId=8b6266a6a8e5656e epId=29372863 gid=ffea4d stats_id=Gwendolyn-5dJ conf_name=ivan] AbstractEndpointMessageTransport.onClientEndpointMessage#219: Unable to find endpoint 88e0378a to send EndpointMessage
2020-04-01 22:59:32.179 WARNUNG: [1177] [confId=8b6266a6a8e5656e epId=29372863 gid=ffea4d stats_id=Gwendolyn-5dJ conf_name=ivan] AbstractEndpointMessageTransport.onClientEndpointMessage#219: Unable to find endpoint 88e0378a to send EndpointMessage
2020-04-01 22:59:40.542 WARNUNG: [1184] [confId=8b6266a6a8e5656e gid=ffea4d stats_id=Gwendolyn-5dJ componentId=1 conf_name=ivan ufrag=a3te41e4ro9kve name=stream-29372863 epId=29372863 local_ufrag=a3te41e4ro9kve] MergingDatagramSocket.doRemove#349: Removing the active socket. Won't be able to send until a new one is elected.

This is the only warning in the jicofo.log

Jicofo 2020-04-03 13:32:21.450 WARNUNG: [30] org.jitsi.jicofo.JitsiMeetConferenceImpl.log() No jingle session yet for ivan@conference.meet.mydomain.de/b911be7f

And these are the messages from prosody.log

Apr 03 13:31:53 conference.meet.mydomain.de:muc_domain_mapper   warn    Session filters applied
Apr 03 13:31:53 mod_bosh        info    New BOSH session, assigned it sid 'c85443d4-f2c3-4f95-997b-05ab0d00a4c4'
Apr 03 13:31:53 boshc85443d4-f2c3-4f95-997b-05ab0d00a4c4        info    Authenticated as _dvkbfdh1svpchdt@meet.mydomain.de
Apr 03 13:32:19 conference.meet.mydomain.de:muc_domain_mapper   warn    Session filters applied
Apr 03 13:32:19 mod_bosh        info    New BOSH session, assigned it sid 'bf61a445-e5f4-436b-b0dc-c0c5aff40f44'
Apr 03 13:32:19 boshbf61a445-e5f4-436b-b0dc-c0c5aff40f44        info    Authenticated as zqcjbvzd04k8-phl@meet.mydomain.de
Apr 03 13:33:35 conference.meet.mydomain.de:muc_domain_mapper   warn    Session filters applied
Apr 03 13:33:35 mod_bosh        info    New BOSH session, assigned it sid 'b3af9568-cbb6-49ea-addf-e671f9cff5ca'
Apr 03 13:33:36 boshb3af9568-cbb6-49ea-addf-e671f9cff5ca        info    Authenticated as m9nrndaoeh8qv13e@meet.mydomain.de
Apr 03 13:34:00 boshc85443d4-f2c3-4f95-997b-05ab0d00a4c4        info    BOSH client disconnected: session close
Apr 03 13:34:02 conference.meet.mydomain.de:muc_domain_mapper   warn    Session filters applied
Apr 03 13:34:02 mod_bosh        info    New BOSH session, assigned it sid '954e10a4-c03f-45de-aaf9-9fbf8ef14c88'
Apr 03 13:34:02 bosh954e10a4-c03f-45de-aaf9-9fbf8ef14c88        info    Authenticated as 0nebqq_92tm4kspg@meet.mydomain.de
Apr 03 13:34:41 bosh954e10a4-c03f-45de-aaf9-9fbf8ef14c88        info    BOSH client disconnected: session close
Apr 03 13:36:32 conference.meet.mydomain.de:muc_domain_mapper   warn    Session filters applied
Apr 03 13:36:32 mod_bosh        info    New BOSH session, assigned it sid '6f943e7f-0a82-48fa-a90b-77604c76cae5'
Apr 03 13:36:32 bosh6f943e7f-0a82-48fa-a90b-77604c76cae5        info    Authenticated as vaew7tladoglwink@meet.mydomain.de
Apr 03 13:37:11 bosh6f943e7f-0a82-48fa-a90b-77604c76cae5        info    BOSH client disconnected: session close
Apr 03 13:37:12 conference.meet.mydomain.de:muc_domain_mapper   warn    Session filters applied
Apr 03 13:37:12 mod_bosh        info    New BOSH session, assigned it sid '64e8ed04-1e79-4251-a127-984c17c266cf'
Apr 03 13:37:12 bosh64e8ed04-1e79-4251-a127-984c17c266cf        info    Authenticated as -fhoxrq01eyukjbn@meet.mydomain.de
Apr 03 13:37:24 bosh64e8ed04-1e79-4251-a127-984c17c266cf        info    BOSH client disconnected: session close
Apr 03 13:37:52 boshbf61a445-e5f4-436b-b0dc-c0c5aff40f44        info    BOSH client disconnected: session close
Apr 03 13:37:59 boshb3af9568-cbb6-49ea-addf-e671f9cff5ca        info    BOSH client disconnected: session close
Apr 03 13:37:59 speakerstats.meet.mydomain.de:speakerstats_component    warn    A module has been configured that triggers external events.
Apr 03 13:37:59 speakerstats.meet.mydomain.de:speakerstats_component    warn    Implement this lib to trigger external events.

Ok, I found the problem.

In the quick-install guide is this mysterious line:

And comment the existing org.ice4j.ice.harvest.STUN_MAPPING_HARVESTER_ADDRESSES

I had followed the quick install to the letter and commented the line

#org.ice4j.ice.harvest.STUN_MAPPING_HARVESTER_ADDRESSES=meet-jit-si-turnrelay.jitsi.net:443

Without this comment it works.
Maybe the quick install guide is wrong?

The quick install says, if you add the

NAT_HARVESTER_LOCAL_ADDRESS
NAT_HARVESTER_PUBLIC_ADDRESS

then comment that line STUN_MAPPING_HARVESTER_ADDRESSES .

Yes I did this.
The relay fallback with jvb does not seem to work…

/etc/jitsi/videobridge/sip-communicator.properties:

org.ice4j.ice.harvest.NAT_HARVESTER_LOCAL_ADDRESS=nameofServer
org.ice4j.ice.harvest.NAT_HARVESTER_PUBLIC_ADDRESS=meet.mydomain.de
org.ice4j.ice.harvest.DISABLE_AWS_HARVESTER=true
#org.ice4j.ice.harvest.STUN_MAPPING_HARVESTER_ADDRESSES=meet-jit-si-turnrelay.jitsi.net:443
org.jitsi.videobridge.ENABLE_STATISTICS=true
org.jitsi.videobridge.STATISTICS_TRANSPORT=muc
org.jitsi.videobridge.xmpp.user.shard.HOSTNAME=localhost
org.jitsi.videobridge.xmpp.user.shard.DOMAIN=auth.meet.mydomain.de
org.jitsi.videobridge.xmpp.user.shard.USERNAME=jvb
org.jitsi.videobridge.xmpp.user.shard.PASSWORD=XXXXXXXX
org.jitsi.videobridge.xmpp.user.shard.MUC_JIDS=JvbBrewery@internal.auth.meet.mydomain.de.de
org.jitsi.videobridge.xmpp.user.shard.MUC_NICKNAME=c89aa2f7-85bc-427c-beb1-104643314ccc

Oh, btw, Port forwarding of NAT configuration:
TCP 443
TCP 4443
TCP 80
UDP 10000