Two broswers/users opened in the same room but they can't see each other

I have installed Jitsi Meet using quick install. Everything worked well until then. Checked the working with 2 and more browsers.
After that I have implemented secure domain following the steps from https://github.com/jitsi/jicofo#secure-domain .
Once its completed , an issue occurred - 2 people joining the same room are unable too see each other . I’m able to see the jitsi page (dark blue background).
I can see myself on the loopback video, etc.

However, I open the same URL (room) on two different browsers but they don’t see themselves as if they are different users. They see themselves as if they are alone in the room.
Checked the console and doesn’t find any errors.

NB: Saw the same issue mentioned in Two broswers opened in the same room but they don't see each other [SOLVED]

I have tried the same as well , but of no use. Please give a solution regarding the same.

Any jicofo or prosody errors?

Yes. Attaching Prosody , Jicofo and Jvb logs below :

PROSODY Logs:

Mar 31 04:23:19 mod_bosh info Client tried to use sid ‘a87bd3f4-eb4f-4177-8e35-3eaaebfcbd56’ which we don’t know about
Mar 31 04:23:20 mod_bosh info Client tried to use sid ‘a87bd3f4-eb4f-4177-8e35-3eaaebfcbd56’ which we don’t know about
Mar 31 04:23:20 mod_bosh info Client tried to use sid ‘a87bd3f4-eb4f-4177-8e35-3eaaebfcbd56’ which we don’t know about
Mar 31 04:23:20 mod_bosh info Client tried to use sid ‘a87bd3f4-eb4f-4177-8e35-3eaaebfcbd56’ which we don’t know about
Mar 31 04:23:21 mod_bosh info Client tried to use sid ‘a87bd3f4-eb4f-4177-8e35-3eaaebfcbd56’ which we don’t know about
Mar 31 04:23:21 mod_bosh info Client tried to use sid ‘a87bd3f4-eb4f-4177-8e35-3eaaebfcbd56’ which we don’t know about
Mar 31 04:23:21 conference.mydomain.com:muc_domain_mapper warn Session filters applied
Mar 31 04:23:21 c2s559ee3f8a6c0 info Client connected
Mar 31 04:23:21 c2s559ee3f8a6c0 info Stream encrypted (TLSv1.2 with ECDHE-RSA-AES256-GCM-SHA384)
Mar 31 04:23:21 c2s559ee3f8a6c0 info Client disconnected: connection closed

JICOFO Logs :
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)
Jicofo 2020-03-31 04:21:14.870 SEVERE: [85] org.jitsi.impl.protocol.xmpp.XmppProtocolProvider.doConnect().315 Failed to connect/login: 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)

JVB Logs:

2020-03-31 04:20:03.508 INFO: [17] Videobridge.createConference#326: create_conf , id=a5f6be40ad799e03 gid=null logging=false
2020-03-31 04:20:03.512 INFO: [17] Health.doRun#294: Performed a successful heal th check in 4ms. Sticky failure: false
2020-03-31 04:20:13.512 INFO: [17] Videobridge.createConference#326: create_conf , id=cae2f8d974213f8 gid=null logging=false
2020-03-31 04:20:13.516 INFO: [17] Health.doRun#294: Performed a successful heal th check in 4ms. Sticky failure: false
2020-03-31 04:20:23.516 INFO: [17] Videobridge.createConference#326: create_conf , id=a1a9ea60cf2416a0 gid=null logging=false
2020-03-31 04:20:23.520 INFO: [17] Health.doRun#294: Performed a successful heal th check in 4ms. Sticky failure: false
2020-03-31 04:20:33.520 INFO: [17] Videobridge.createConference#326: create_conf , id=5cf34944e7d2d253 gid=null logging=false
2020-03-31 04:20:33.524 INFO: [17] Health.doRun#294: Performed a successful heal th check in 4ms. Sticky failure: false
2020-03-31 04:20:43.524 INFO: [17] Videobridge.createConference#326: create_conf , id=68db7b754d8228cc gid=null logging=false
2020-03-31 04:20:43.528 INFO: [17] Health.doRun#294: Performed a successful heal th check in 4ms. Sticky failure: false

This is jicofo user password is wrong. This one: jicofo/postinst at master · jitsi/jicofo · GitHub

Hi,
I have fixed the above mentioned issue and everything worked fine. I have then implemented jwt plugin using https://github.com/jitsi/lib-jitsi-meet/blob/master/doc/tokens.md . After the setup, but
when I try to login with a token I cannot login to the conference and
getting following in prosody.log :

warn No available SASL mechanisms, verify that the configured

Also I have error in log files. Attaching the log files below:

prosody log :

Apr 04 12:15:22 c2s562d4863ff40 info Client connected
Apr 04 12:15:22 c2s562d4863ff40 info Stream encrypted (TLSv1.2 with ECDHE-RSA-AES256-GCM-SHA384)
Apr 04 12:15:22 c2s562d4863ff40 info Authenticated as jvb@auth.jitsi.example.com
Apr 04 12:15:36 conference.video.jitsi.example.com:muc_domain_mapper warn Session filters applied
Apr 04 12:15:36 mod_bosh info New BOSH session, assigned it sid ‘c5999543-6ce6-4c50-82fb-3c8b3f08dd39’
Apr 04 12:15:36 boshc5999543-6ce6-4c50-82fb-3c8b3f08dd39 warn No available SASL mechanisms, verify that the configured authentication module is working
Apr 04 12:16:53 boshc5999543-6ce6-4c50-82fb-3c8b3f08dd39 info BOSH client disconnected
Apr 04 12:17:22 conference.video.jitsi.example.com:muc_domain_mapper warn Session filters applied
Apr 04 12:17:22 mod_bosh info New BOSH session, assigned it sid ‘472565a7-8ad3-4a6a-b6a9-5a072a7a2eaa’
Apr 04 12:17:22 bosh472565a7-8ad3-4a6a-b6a9-5a072a7a2eaa warn No available SASL mechanisms, verify that the configured authentication module is working

jicofo log :

Jicofo 2020-04-04 12:15:18.001 INFO: [42] org.jitsi.jicofo.bridge.BridgeSelector.log() Added videobridge: jitsi-videobridge.video.jitsi.example.com v: IQ Stanza (query jabber:iq:version) [to=focus@auth.video.jitsi.example.com/focus85642887873933,from=jitsi-videobridge.jitsi.example.com,id=QE251-81,type=result,]
Jicofo 2020-04-04 12:15:18.001 WARNING: [42] org.jitsi.jicofo.bridge.BridgeSelector.log() No pub-sub node mapped for jitsi-videobridge.jitsi.example.com
Jicofo 2020-04-04 12:15:18.001 INFO: [42] org.jitsi.jicofo.ComponentsDiscovery.log() Services re-discovery interval: 30000
Jicofo 2020-04-04 12:15:18.001 INFO: [42] org.jitsi.jicofo.FocusManager.log() XMPP provider reg state: RegistrationState=Registered
Jicofo 2020-04-04 12:15:18.006 INFO: [43] org.jitsi.jicofo.bridge.JvbDoctor.log() Scheduled health-check task for: jitsi-videobridge.video.jitsi.example.com
Jicofo 2020-04-04 12:15:22.417 SEVERE: [45] org.jitsi.xmpp.component.ComponentBase.log() Ping timeout for ID: QE251-51
Jicofo 2020-04-04 12:15:22.980 INFO: [28] org.jitsi.jicofo.xmpp.BaseBrewery.processInstanceStatusChanged().329 Added brewery instance: jvbbrewery@internal.auth.video.jitsi.example.com/d086a665-0db1-48a2-aee8-f60a2e83e4bb
Jicofo 2020-04-04 12:15:22.980 INFO: [28] org.jitsi.jicofo.bridge.BridgeSelector.log() Added videobridge: jvbbrewery@internal.auth.video.jitsi.example.com/d086a665-0db1-48a2-aee8-f60a2e83e4bb v: null
Jicofo 2020-04-04 12:15:22.981 WARNING: [28] org.jitsi.jicofo.bridge.BridgeSelector.log() No pub-sub node mapped for jvbbrewery@internal.auth.video.jitsi.example.com/d086a665-0db1-48a2-aee8-f60a2e83e4bb
Jicofo 2020-04-04 12:15:22.986 INFO: [43] org.jitsi.jicofo.bridge.JvbDoctor.log() Scheduled health-check task for: jvbbrewery@internal.auth.video.jitsi.example.com/d086a665-0db1-48a2-aee8-f60a2e83e4bb

DEBUGGING Prosody :

root@ip-172-31-14-21:~# tail /var/log/prosody/prosody.log
Apr 04 12:58:38 conference.video.jitsi.example.com:muc_domain_mapper debug No need to rewrite jvb@auth.video.jitsi.example.com/bc15459c-2a7b-4c5d-94c6-aa3f38b1944d (not from the MUC host) yioA9-37125, nil
Apr 04 12:58:38 internal.auth.video.jitsi.example.com:muc debug presence updatefor jvbbrewery@internal.auth.video.jitsi.example.com/d086a665-0db1-48a2-aee8-f60a2e83e4bb from session jvb@auth.video.jitsi.example.com/bc15459c-2a7b-4c5d-94c6-aa3f38b1944d
Apr 04 12:58:38 conference.video.jitsi.example.com:muc_domain_mapper debug No need to rewrite jvbbrewery@internal.auth.video.jitsi.example.com/d086a665-0db1-48a2-aee8-f60a2e83e4bb (not from the MUC host) yioA9-37125, nil
Apr 04 12:58:38 conference.video.jitsi.example.com:muc_domain_mapper debug Filterin g stanza type presence to focus@auth.video.jitsi.example.com/focus85642887873933 from jvbbrewery@internal.auth.video.jitsi.example.com/d086a665-0db1-48a2-aee8-f60a2e83e4bb
Apr 04 12:58:38 conference.video.jitsi.example.com:muc_domain_mapper debug No need to rewrite out ‘to’ focus@auth.video.jitsi.example.com/focus85642887873933
Apr 04 12:58:38 conference.video.jitsi.example.com:muc_domain_mapper debug No need to rewrite jvbbrewery@internal.auth.video.jitsi.example.com/d086a665-0db1-48a2-aee8-f60a2e83e4bb (not from the MUC host) yioA9-37125, nil
Apr 04 12:58:38 conference.video.jitsi.example.com:muc_domain_mapper debug No need to rewrite jvbbrewery@internal.auth.video.jitsi.example.com/d086a665-0db1-48a2-aee8-f60a2e83e4bb (not from the MUC host) yioA9-37125, nil
Apr 04 12:58:38 conference.video.jitsi.example.com:muc_domain_mapper debug Filtering stanza type presence to jvb@auth.video.jitsi.example.com/bc15459c-2a7b-4c5d-94c6-aa3f38b1944d from jvbbrewery@internal.auth.video.jitsi.example.com/d086a665-0db1-48a2-aee8-f60a2e83e4bb
Apr 04 12:58:38 conference.video.jitsi.example.com:muc_domain_mapper debug No need to rewrite out ‘to’ jvb@auth.video.jitsi.example.com/bc15459c-2a7b-4c5d-94c6-aa3f38b1944d
Apr 04 12:58:38 conference.video.jitsi.example.com:muc_domain_mapper debug No need to rewrite jvbbrewery@internal.auth.video.jitsi.example.com/d086a665-0db1-48a2-aee8-f6 0a2e83e4bb (not from the MUC host) yioA9-37125, nil

prosody.err :

(tail call): ?
/usr/lib/prosody/core/hostmanager.lua:104: in function ‘activate’
/usr/lib/prosody/core/hostmanager.lua:57: in function ‘?’
/usr/lib/prosody/util/events.lua:78: in function </usr/lib/prosody/util/events.lua:74>
(tail call): ?
/usr/bin/prosody:354: in function ‘prepare_to_start’
/usr/bin/prosody:423: in main chunk
[C]: ?
Apr 03 12:27:56 portmanager error Error binding encrypted port for https: No key present in SSL/TLS configuration for https port 5281
Apr 03 12:27:56 portmanager error Error binding encrypted port for https: No key present in SSL/TLS configuration for https port 5281

I couldn’t find a solution. Can you please help?? @damencho

Where do I change this @damencho ? In /etc/jitsi/jicofo/config? If so how do I know what to change it too?

The passwords are stored under /var/lib/prosody/…

1 Like