Hi Team.
I did quick_install jitsi-meet. when i demo kick participant error.
thanks.
Hi Team.
I did quick_install jitsi-meet. when i demo kick participant error.
thanks.
Can you expand the error, to see what is the actual error? Which version of prosody do you use?
Can you send the error or log as text, it is still not visible, you need to expand the iq message, there is content inside, which is hidden.
Hum, you are using the all moderators prosody plugin.
Did you apply this patch to your prosody: https://github.com/jitsi/jitsi-meet/blob/b01ad360da76d12538cd4070b23d1b891b8f70e9/resources/prosody-plugins/muc_owner_allow_kick.patch
The patch is against trunk prosody version, so you need to find and apply a similar patch in prosody 0.9.1 codebase.
Thanks for replying. I will try your guide.
Kick participant error: facing same issue
hello @damencho how to apply patch
https://github.com/jitsi/jitsi-meet/blob/b01ad360da76d12538cd4070b23d1b891b8f70e9/resources/prosody-plugins/muc_owner_allow_kick.patch
I’m seeing this problem too. Here is the data from my log:
<iq xmlns="jabber:client" type="error" id="1d07440f-3378-453e-8d44-d59845b384b6:sendIQ" to="wm53ktsd_osnnncv@guest.jitsi401.mydomain.com/Y3z5o31j" from="meeting-b51baa00-e5ca-4af4-a862-500d71ac026f@conference.jitsi401.mydomain.com"><error type="cancel"><not-allowed xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/></error></iq>
I believe we are using the all moderators plugin. How can you tell from these logs? If so I suppose we need to apply the patch.
I found the muc.lib.lua file in /usr/lib/prosody/modules/muc folder. To apply the patch, open that vile and change the lines specified in the patch.