New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
relayId coming as 0.0.0.0 from after stable-7287-2 jvb images #1349
Comments
I honestly have no idea :-/ @bgrozev can you enlighten us here? |
@bgrozev is this might be the issue |
@bgrozev even if relayid is there it is getting a fallback to bind address |
Sorry, I'm not sure what breaks, but it's best to simply update to the latest config scheme. Something like:
I'm not sure what the best way to set the ID in a docker setup is. It just needs to be unique in the set of jvb's connected to jicofo. Taking $JVB_MUC_NICKNAME might work, or whatever was used to set bind-address. We can get rid of .Env.JVB_OCTO_BIND_ADDRESS, .Env.JVB_OCTO_PUBLIC_ADDRESS, and .Env.JVB_OCTO_BIND_PORT. |
|
Thanks I'll update the config! |
Continues on #1371 |
@saghul relay id is still coming as 0.0.0.0 in latest jitsi/jvb:stable-7648-4 image |
Did you set JVB_OCTO_RELAY_ID ? |
Right, my bad! I just noticed the PR is not merged, I'll do that now. |
Hi @saghul ,
After jvb release 7287-2 ie, in stable-7439 and stable-7439-2. the relayid shown in jicofo logs is as 0.0.0.0.
I think the relay id is being picked up from here in the last two releases.
when I change the bind address the relay id in jicofo is changing.
Any way to change the relayid to JVB_OCTO_PUBLIC_ADDRESS?
The text was updated successfully, but these errors were encountered: