So Jicofo healthcheck jvb periodically and if it is unhealthy it is
removed from the pool of jvbs that it can use. In the logs(jicofo and
jvb) there is an exception and the response to the filed healthcheck:
xmlns="urn:ietf:params:xml:ns:xmpp-stanzas" xml:lang="en">Failed to
bind even a single host candidate for component:Component id=1 parent
no local candidates.
no remote candidates. preferredPort=10769 minPort=10769
As your jvb has only one interface (excluding local addresses like
localhost and link-local), at the moment when this happend this
interface was down.
So restarting jicofo will fix the problem.
Thanks for the report. We will fix the exception, at least it should
not happen, and maybe add some log so we can more easily identify such
problems. But this case is valid one if there are no usable interfaces
- jvb is unhealthy.
On Thu, Mar 22, 2018 at 9:28 AM, Bruno Konik <email@example.com> wrote:
We are new to Jitsi Meet and would like to install and run Jitsi Meet for
our local network only. We installed it on Debian with Nginx installed
Our host is debian.unigone.local, we followed the quick install. We chose to
generate a new self-signed certificate as proposed by the installation.
Once installation is done, there seems to be errors but one user can
successfully access the Jitsi meet page. As soon as the second user tries to
enter the room, the connection fails for both (and tries to reconnect
I have attached the logs.
If someone can have a look at them and let me know what is wrong in our
installation, thank you!
users mailing list
Unsubscribe instructions and other list options: