Suddenly 2nd participant gives "reconnecting" on first and second screen
See original GitHub issueJitsi have been working ok for some months, but after last Friday docker-compose up -d --force-recreate
:
- first participant shows working setup and own webcam image
- as soon as 2nd participant arrives, both screens get grey (or red screen on Android) and a reconnecting timer shows.
I just cloned latest repo, but no result…
Issue Analytics
- State:
- Created 5 years ago
- Reactions:3
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Dual Screen constantly reconnecting & disconnecting on startup
1. Run the Hardware Troubleshooter by pressing CTRL+SHIFT+ESC keys together >click File menu > click "Run new task" > type cmd & tick...
Read more >The most common multi-monitor problems and how to fix them
Force Windows to detect your monitor : Maybe Windows didn't recognize your second display's connection. To force it to check again, right-click ...
Read more >Can no longer detect 2nd display i… | Apple Developer Forums
I am a photographer and my livelihood depends on my editing which I do on the external monitor. Now suddenly after the update...
Read more >Why Does My Monitor Keep Going Black - How To Fix It
If replacing the cable does not solve the problem, try the second port – some monitors have two ports, one for HDMI and...
Read more >Laptop can't detect second monitor - HP Support Community
press the Windows logo key + P (Or Fn key + F4) and check if the setting is chosen to “Extend” the screen...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Got it working. After tip from @saghul in https://github.com/jitsi/docker-jitsi-meet/issues/15 I removed folder
rm -rf ~/.jitsi-meet-cfg
to activate my.env
changes:DISABLE_HTTPS=1
I am running on nginx proxy and now forward to http instead of https. Dont know if that was main cause, just guessing for now. That said, I dont think it is elegant that you need to remove a folder on host after an configuration change… I would think it is possible to keep config in one place only so container updates become predictable and repeatable over various configurations and we don’t get state differences …
No worries!