jicofo config looks like this
# Jitsi Conference Focus settings
# sets the host name of the XMPP server
# sets the XMPP domain (default: none)
# sets the secret used to authenticate as an XMPP component
# sets the port to use for the XMPP component connection
# sets the XMPP domain name to use for XMPP user logins
# sets the username to use for XMPP user logins
# sets the password to use for XMPP user logins
# extra options to pass to the jicofo daemon
# adds java system props that are passed to jicofo (default are for home and logging config file)
JAVA_SYS_PROPS="-Dnet.java.sip.communicator.SC_HOME_DIR_LOCATION=/etc/jitsi -Dnet.java.sip.communicator.SC_HOME_DIR_NAME=jicofo -Dnet.java.sip.communicator.SC_LOG_DIR_LOCATION=/v$
This is the exact issue I’m facing, the prosody logs getting this “bounce-error” every 30 seconds
As I understand your answers, this is due to a bug and NOT a configuration error. I quote:
So, you can try start all from scratch, by uninstalling, deleting /var/lib/prosody contents, restart prosody and install jitsi-meet again.
There is a bug we know about and we are fixing it.
Since the system seems to work fine, users(and more than 2) can join rooms etc, I have a few questions
This bug must have an impact somehow? What should we expect not to work?
Should I just leave it alone and wait for a fix?
Is there a definite workaround instead of wiping /var/lib/prosody and reinstalling jitsi-meet. And when you write install jitsi-meet again do you mean something like: sudo apt --reinstall install jitsi-meet.
I’m not so fond of tearing everything down, since the system is being used - but maybe not so much in the week-end…
Hey, just interested (as I get the same error, and same as you everything working nonetheless) why you are looking at the jicofo sip-communicator.properties while the error message states that jitsi-videobridge is throwing the error (as far as I understand). Is it because at the end of the error message the “from” states ‘focus@auth…’?
I get no error messages in my /var/log/jitsi/jicofo.log, only the info that successfull health checks where performed.
There is another thread here where the error message states: focus.mydomainhere.com:component warn Component not connected, bouncing error for: <iq id='gEXV7-53' type='get' to='focus.mydomainhere.com' email@example.com/focus6292778556840'>
I get this specific error only once, when I start the jicofo service (after starting prosody and jvb, in this order).
[Edit] Oops, I removed the component definition by commenting out the segment Component "focus.jitsi.domain.com" from /etc/prosody/conf.avail/jitsi.domain.com.cfg.lua instead of Component "jitsi-videobridge.jitsi.domain.com"… that got me errors in the prosody.log I specified here before the edit, now it’s working and the component error is not showing anymore. [/Edit]
To all: How should the /etc/jitsi/videobridge/config look like? Should there be this options: JVB_AUTH_DOMAIN=auth.jitsi.domain.com JVB_AUTH_USER=jvb JVB_AUTH_PASSWORD=passwordxyz
Or are the credentials only needed in /etc/jitsi/videobridge/sip-communicator.properties as org.jitsi.videobridge.xmpp.user.shard.DOMAIN=auth.jitsi.domain.com org.jitsi.videobridge.xmpp.user.shard.USERNAME=jvb org.jitsi.videobridge.xmpp.user.shard.PASSWORD=passwordxyz
because JVB uses now MUCS instead of Component?