search

jitsi / docker-jitsi-meet

Jitsi Meet on Docker
https://hub.docker.com/u/jitsi/
Apache License 2.0
3.06k stars 1.36k forks source link

Web client fails to join or create rooms with fresh docker install #668

Open davebenvenuti opened 4 years ago

davebenvenuti commented 4 years ago

I followed the instructions here to create a new jitsi server. Using the web client to create a room on a fresh install produces the following Javascript error:

VM144 react_devtools_backend.js:6 2020-07-05T19:16:03.811Z [JitsiMeetJS.js] <Object.getGlobalOnErrorHandler>:  UnhandledError: null Script: null Line: null Column: null StackTrace:  Error: Focus error, retry after 1000
    at u._allocateConferenceFocusError (VM133 lib-jitsi-meet.min.js:10)
    at VM133 lib-jitsi-meet.min.js:10
    at I.Handler.handler (VM133 lib-jitsi-meet.min.js:1)
    at I.Handler.run (VM133 lib-jitsi-meet.min.js:1)
    at VM133 lib-jitsi-meet.min.js:1
    at Object.forEachChild (VM133 lib-jitsi-meet.min.js:1)
    at I.Connection._dataRecv (VM133 lib-jitsi-meet.min.js:1)
    at D.Bosh._onRequestStateChange (VM133 lib-jitsi-meet.min.js:1)

Which results in an "Unfortunately, something went wrong. We're trying to fix this" message with a progress bar. When the progress bar completes, the page refreshes, and we get the same error. Here is the version information for the docker containers:

REPOSITORY          TAG                 IMAGE ID            CREATED             SIZE
jitsi/jvb           latest              ff366d6653e3        5 weeks ago         278MB
jitsi/jicofo        latest              8a99d30ab075        5 weeks ago         292MB
jitsi/prosody       latest              50f5c1e719aa        5 weeks ago         106MB
jitsi/web           latest              7de9a63e7e82        5 weeks ago         483MB

In the .env, I edited the http and https ports, the PUBLIC_URL, lets encrypt entries, and enabled https redirect. And ran the script to generate secure passwords. Let me know if there's any other information you need. A previous version of the docker setup worked fine for us. Thanks

johanleroch commented 4 years ago

Same issue for me, working well in local but reproducing this issue through scaleway and aws (docker)