Mic & video goes off on a running conference if participant count is more than 2

We installed Jitsi successfully using local ip e.g: 192.168…, here hostname is auth.localip and p2p & jingle/conference session both are working fine.
Suddenly, our network configuration changed by system admin and later we want to use our existing established Jitsi server to communicate each other. But we failed to do P2P and conference session.
After lots of R&D we changed some config file with the new IP. Changed files are-

  • /etc/jitsi/meet/ip-config.js,
  • /etc/jitsi/jicofo/config,
  • /etc/jitsi/videobridge/config
  • nginx
  • /etc/prosody/conf.d/ip.lua

And then we can do P2P session but when another participant join to that running conference then the mic & video goes off of all the participants but 3 thumbnails available are on the screen.
Again, we did some R&D on that and seen the jicofo log and there we got xmpp host verifier() cannot match the cert with new IP.

Please do some help to relieve from the issue.

Add to jicofo configuration (/etc/jitsi/jicofo/sip-communicator.properties)
org.jitsi.jicofo.ALWAYS_TRUST_MODE_ENABLED=true
and restart jicofo (maybe give some time for jicofo to discover the bridge).

I already did but still no hope.
I found following error on jicofo log:
Jicofo 2019-04-29 23:04:59.314 WARNING: [38] org.jivesoftware.smack.roster.Roster.processStanza() Roster not loaded while processing$
Jicofo 2019-04-29 23:05:04.380 SEVERE: [79] org.jitsi.impl.protocol.xmpp.XmppProtocolProvider.doConnect().319 Failed to connect/logi$
org.jivesoftware.smack.sasl.SASLErrorException: SASLError using SCRAM-SHA-1: not-authorized
at org.jivesoftware.smack.SASLAuthentication.authenticationFailed(SASLAuthentication.java:291)
at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader.parsePackets(XMPPTCPConnection.java:1096)
at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader.access$300(XMPPTCPConnection.java:994)
at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader$1.run(XMPPTCPConnection.java:1010)
at java.lang.Thread.run(Thread.java:748)
Jicofo 2019-04-29 23:05:04.382 WARNING: [38] org.jivesoftware.smack.roster.Roster.processStanza() Roster not loaded while processing$
and on the prosody log:
Apr 29 23:12:26 jcp16b7020 info Incoming Jabber component connection
Apr 29 23:12:26 focus.192.168.102.240:component info External component successfully authenticated
Apr 29 23:12:37 mod_bosh info New BOSH session, assigned it sid ‘39870b34-9fb7-42bf-b5ec-be62cad18705’
Apr 29 23:12:37 bosh39870b34-9fb7-42bf-b5ec-be62cad18705 info Authenticated as 49dc4d58-f250-4436-b1f1-49fa296e2016@192.16$
Apr 29 23:12:39 jcp18d50e0 info Incoming Jabber component connection
Apr 29 23:12:39 jitsi-videobridge.192.168.102.240:component info External component successfully authenticated
Apr 29 23:12:41 mod_bosh info New BOSH session, assigned it sid ‘4433e80e-7723-4ed3-9aaf-f8d469f2221e’
Apr 29 23:12:41 bosh4433e80e-7723-4ed3-9aaf-f8d469f2221e info Authenticated as 304d1f65-5d34-4bb4-a147-89ce5a9eeaf9@192.16$
Apr 29 23:12:42 c2s194aba0 info Client connected
Apr 29 23:12:42 c2s194aba0 info Stream encrypted (TLSv1.2 with ECDHE-RSA-AES256-GCM-SHA384)
Apr 29 23:12:44 c2s194aba0 info Client disconnected: connection closed
Apr 29 23:12:49 c2s19e5c50 info Client connected
Apr 29 23:12:49 c2s19e5c50 info Stream encrypted (TLSv1.2 with ECDHE-RSA-AES256-GCM-SHA384)
Apr 29 23:12:49 c2s19e5c50 info Client disconnected: connection closed
Apr 29 23:12:54 c2s1b0b940 info Client connected
Apr 29 23:12:54 c2s1b0b940 info Stream encrypted (TLSv1.2 with ECDHE-RSA-AES256-GCM-SHA384)
Apr 29 23:12:54 c2s1b0b940 info Client disconnected: connection closed
Apr 29 23:12:59 c2s1b33ac0 info Client connected
Apr 29 23:12:59 c2s1b33ac0 info Stream encrypted (TLSv1.2 with ECDHE-RSA-AES256-GCM-SHA384)
Apr 29 23:12:59 c2s1b33ac0 info Client disconnected: connection closed
Apr 29 23:13:04 c2s1b57d80 info Client connected
Apr 29 23:13:05 c2s1b57d80 info Stream encrypted (TLSv1.2 with ECDHE-RSA-AES256-GCM-SHA384)
Apr 29 23:13:05 c2s1b57d80 info Client disconnected: connection closed
Apr 29 23:13:10 c2s1b7ff70 info Client connected
Apr 29 23:13:10 c2s1b7ff70 info Stream encrypted (TLSv1.2 with ECDHE-RSA-AES256-GCM-SHA384)
Apr 29 23:13:10 c2s1b7ff70 info Client disconnected: connection closed
Apr 29 23:13:13 mod_bosh info New BOSH session, assigned it sid ‘9bdd71bd-b02a-4099-942f-6881ac2fea01’
Apr 29 23:13:13 bosh9bdd71bd-b02a-4099-942f-6881ac2fea01 info Authenticated as 7a4f8fe7-c104-4d16-9f8f-18ff603b6119@192.16$
Apr 29 23:13:15 c2s17e63d0 info Client connected
Apr 29 23:13:15 c2s17e63d0 info Stream encrypted (TLSv1.2 with ECDHE-RSA-AES256-GCM-SHA384)
Apr 29 23:13:15 c2s17e63d0 info Client disconnected: connection closed
Apr 29 23:13:20 c2s1843050 info Client connected
Apr 29 23:13:20 c2s1843050 info Stream encrypted (TLSv1.2 with ECDHE-RSA-AES256-GCM-SHA384)
Apr 29 23:13:20 c2s1843050 info Client disconnected: connection closed

Check that the passwords in this file are correct.

Sorry for the delay response. Checked that and its ok.
I also matched with the prosody account password and both are same.

This for me is a wrong client password. This is controlled by JICOFO_AUTH_DOMAIN, JICOFO_AUTH_USER and JICOFO_AUTH_PASSWORD
The user should be JICOFO_AUTH_USER@JICOFO_AUTH_DOMAIN
Can you double check it like this:

. /etc/jitsi/jicofo/config
cat /var/lib/prosody/"${JICOFO_AUTH_DOMAIN//\./\%2e}"/accounts/${JICOFO_AUTH_USER}.dat |  grep -c ${JICOFO_AUTH_PASSWORD} 

Do you see 0 or 1 as output?

I got 1

So maybe that is just an old error you had already fixed (SASLError using SCRAM-SHA-1: not-authorized).

Since the ip address change, have you restarted jvb?

Yes. Restart the PC also

Open chrome://webrtc-internals before starting the call. And when you open the call and there is no media, check the last setRemoteDescription do you see the correct ip address and port of the bridge that the webrtc will use to send data.