Suddenly 2nd participant gives "reconnecting" on first and second screen

jitsi / docker-jitsi-meet

Jitsi Meet on Docker

https://hub.docker.com/u/jitsi/

Apache License 2.0

3.09k stars 1.37k forks source link

Suddenly 2nd participant gives "reconnecting" on first and second screen #38

Closed tvld closed 5 years ago

tvld commented 5 years ago

screenshot from 2018-12-04 20-52-23

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

tvld commented 5 years ago

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

saghul commented 5 years ago

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

I don't disagree :-) I'll look into lifting this limitation.

tvld commented 5 years ago

I'll look into lifting this limitation.

Excellent.

When you are at it, maybe also think for a moment about the .gitignore for .env? As for us, there's nothing that needs to be kept secure in that file.

Idea Maybe replace .env with two files:

an optional file secure.env which is in .gitignore: this file would overwrite duplicate settings in:
config.env, copy of the current .env file

This approach would remove the need to keep the .env and example.env files. Which is appreciated as .env file put me off track when first installing: I never saw the hidden .env in the Linux folder...

saghul commented 5 years ago

Well, that would mean the command people need to type to run this is longer, for not a good reason. The choice for .env is not arbitrary, is what Docker Compose picks up by default.

There are certainly things you want to be secret, such as the SIP password for Jigasi.

tvld commented 5 years ago

Sounds logical.. so I like to retract my last thoughts ;)))) Sorry ))

saghul commented 5 years ago

No worries!