We have used Kubernetes and docker for setup. It works fine, But from the last 3 days, I am facing a meeting disconnected error. When I checked prosody logs I found
> focus.meet.example.com:component warn Component not connected, bouncing error for: <iq from='61dbded5-230d-465e-a7f9-3a5877d1de7a@guest.meet.example.com/0jmKY_jM' type='set' to='focus.meet.example.com' id='274d5acf-7c26-4555-9bc0-dea57a0b7a7e:sendIQ'>
When I try to restart jicofo
I got this in prosody
c2s55d119515870 info Authenticated as focus@auth.meet.example.com mod_bosh61dbded5-230d-465e-a7f9-3a5877d1de7a@guest.meet.example.com
seems prosody is connected to jicofo but still call disconnected.
Apart from this, there is nothing on jicofo and jvb log.
I have already checked Warn Component not connected, bouncing error .
@damencho @saghul
We are no longer using components for few years now.
Is your prosody config for focus like this:
muc_room_locking = false
muc_room_default_public_jids = true
VirtualHost "auth.jitmeet.example.com"
modules_enabled = {
"limits_exception";
}
authentication = "internal_hashed"
-- Proxy to jicofo's user JID, so that it doesn't have to register as a component.
Component "focus.jitmeet.example.com" "client_proxy"
target_address = "focusUser@auth.jitmeet.example.com"
Component "speakerstats.jitmeet.example.com" "speakerstats_component"
muc_component = "conference.jitmeet.example.com"
Component "conferenceduration.jitmeet.example.com" "conference_duration_component"
muc_component = "conference.jitmeet.example.com"
Component "avmoderation.jitmeet.example.com" "av_moderation_component"
muc_component = "conference.jitmeet.example.com"
1 Like
There is a secret in the prosody config file for focus component its look like
Component “focus.meet.example.com ”
As advised, connection is no longer being made through components. You might want to update your deployment accordingly.
Okay, thank you I will update the configuration. And check how it reacts.
How did you update your deployment, this change is handled by the update?
PROSODY_CONFIG_PRESENT="false"
fi
if ! grep -q -- 'unlimited_jids' $PROSODY_HOST_CONFIG ;then
sed -i "1s/^/unlimited_jids = { \"$JICOFO_AUTH_USER@$JICOFO_AUTH_DOMAIN\", \"jvb@$JICOFO_AUTH_DOMAIN\" }\n/" $PROSODY_HOST_CONFIG
sed -i "s/VirtualHost \"$JICOFO_AUTH_DOMAIN\"/VirtualHost \"$JICOFO_AUTH_DOMAIN\"\n modules_enabled = { \"limits_exception\"; }/g" $PROSODY_HOST_CONFIG
PROSODY_CONFIG_PRESENT="false"
fi
# Make sure the focus@auth user's roster includes the proxy component (this is idempotent)
prosodyctl mod_roster_command subscribe focus.$JVB_HOSTNAME $JICOFO_AUTH_USER@$JICOFO_AUTH_DOMAIN
if [ ! -f /var/lib/prosody/$JVB_HOSTNAME.crt ]; then
# prosodyctl takes care for the permissions
# echo for using all default values
echo | prosodyctl cert generate $JVB_HOSTNAME
ln -sf /var/lib/prosody/$JVB_HOSTNAME.key /etc/prosody/certs/$JVB_HOSTNAME.key
ln -sf /var/lib/prosody/$JVB_HOSTNAME.crt /etc/prosody/certs/$JVB_HOSTNAME.crt
fi
1 Like
I have not touched jicofo and prosody. I will update accordingly. Thank you for the reply.
@damencho I have updated the deployment. Now facing
Jicofo 2022-03-16 12:28:39.328 WARNING: [53] FocusManager.conferenceRequest#249: Exception while trying to start the conferenceconference.meet.example.com : XMPPError: not-allowed - cancel [Communication with remote domains is not enabled]Jibri-Jitsi Connectivity issue on Kubernetes setup - #2 by Anshul_Sehgal
but I am unable to find conference.meet.example.com in any configuration. I am not sure what I am missing.
Please help me out on this.
Show your jicofo configs.
jicofo.txt (1.5 KB)
Thank You I have uploaded the configuration please have a look.
@damencho thank you for the support I have misconfigured the prosody config file. I have fixed it now its working.
1 Like