You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I want to join a meeting hosted on a jistsi docker configured for LAN, the message “You have been disconnected … will reconnect in X seconds” appears. This happens on the host machine and on all machines in LAN.
Otherwise, when I keep the initial config files everything works well on my host machine (ubuntu 22.04).
Configuration
In my .env file:
I just added JVB_ADVERTISE_IPS=192.168.1.48 and my PUBLIC_URL=https://meet.local for which I self-signed a certificate following this tuto: https://www.youtube.com/watch?v=T5VRmlKuJks. Browsers on all machines trust it because I added a certificate authority to them.
I also added 192.168.1.48 meet.local to /etc/hosts client and host machines files.
Could you help me to find the issue? Maybe my .env configuration is wrong for LAN environment meetings. Or it could be because of the TLS certificate self-signed that I ended up doing because Let’s Encrypt embed in Jitsi didn’t work for me. With Let’s Encrypt, I could join meetings on host machine but not on LAN machines because of invalid TLS certificate (browser logs displayed that when I clicked on Join meeting in a room).
The text was updated successfully, but these errors were encountered:
Strongly recommand rm the ~/.jitsi-meet-cfg/ and create them again
I just fix this problem on my server
If your host https port is not 443,you shall clearly define in PUBLIC_URL
Its not mentioned in https://jitsi.github.io/handbook/docs/devops-guide/devops-guide-docker/, i dont know why.
Problem encountered
When I want to join a meeting hosted on a jistsi docker configured for LAN, the message “You have been disconnected … will reconnect in X seconds” appears. This happens on the host machine and on all machines in LAN.
Otherwise, when I keep the initial config files everything works well on my host machine (ubuntu 22.04).
Configuration
In my
.env
file:I just added
JVB_ADVERTISE_IPS=192.168.1.48
and myPUBLIC_URL=https://meet.local
for which I self-signed a certificate following this tuto: https://www.youtube.com/watch?v=T5VRmlKuJks. Browsers on all machines trust it because I added a certificate authority to them.I also added
192.168.1.48 meet.local
to/etc/hosts
client and host machines files.In my
docker-compose.yml
file:- I added logging part as mentioned here https://jitsi.github.io/handbook/docs/devops-guide/devops-guide-docker#accessing-server-logs.
- Self-signed TLS certificate: cert.crt and cert.key (public key) files as explained here https://jitsi.github.io/handbook/docs/devops-guide/devops-guide-docker#using-existing-tls-certificate-and-key.
Logs
Containers logs:
jicofo.log
jvb.log
prosody.log
web.log
Google chrome logs: (client and host)
browser_client_machine.log
browser_host_machine.log
Could you help me to find the issue? Maybe my
.env
configuration is wrong for LAN environment meetings. Or it could be because of the TLS certificate self-signed that I ended up doing because Let’s Encrypt embed in Jitsi didn’t work for me. With Let’s Encrypt, I could join meetings on host machine but not on LAN machines because of invalid TLS certificate (browser logs displayed that when I clicked on Join meeting in a room).The text was updated successfully, but these errors were encountered: