Skip to content
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

You have been disconnected – LAN environment. #1636

Open
gitoror opened this issue Nov 2, 2023 · 1 comment
Open

You have been disconnected – LAN environment. #1636

gitoror opened this issue Nov 2, 2023 · 1 comment

Comments

@gitoror
Copy link

gitoror commented Nov 2, 2023

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 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.

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).

@silverhunter789
Copy link

if in your .env
HTTPS_PORT=8443
then PUBLIC_URL shall be
PUBLIC_URL=https://meet.local:8443

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants