docker-jitsi-meet
docker-jitsi-meet copied to clipboard
jitsi
Docker instructions and/or container broken
Followed instrructions here: https://jitsi.github.io/handbook/docs/devops-guide/devops-guide-docker
Ran
docker-compose up
Get this output:
docker-jitsi-meet-stable-6826-jicofo-1 | INFO: Started ServerConnector@2bc9a775{HTTP/1.1, (http/1.1)}{0.0.0.0:8888}
docker-jitsi-meet-stable-6826-jicofo-1 | Jan 25, 2022 2:32:42 AM org.eclipse.jetty.server.Server doStart
docker-jitsi-meet-stable-6826-jicofo-1 | INFO: Started @1312ms
docker-jitsi-meet-stable-6826-jvb-1 | Jan 25, 2022 2:32:42 AM org.eclipse.jetty.server.handler.ContextHandler doStart
docker-jitsi-meet-stable-6826-jvb-1 | INFO: Started o.e.j.s.ServletContextHandler@6f798482{/,null,AVAILABLE}
docker-jitsi-meet-stable-6826-jvb-1 | Jan 25, 2022 2:32:42 AM org.eclipse.jetty.server.AbstractConnector doStart
docker-jitsi-meet-stable-6826-jvb-1 | INFO: Started ServerConnector@6c000e0c{HTTP/1.1, (http/1.1)}{0.0.0.0:8080}
docker-jitsi-meet-stable-6826-jvb-1 | Jan 25, 2022 2:32:42 AM org.eclipse.jetty.server.Server doStart
docker-jitsi-meet-stable-6826-jvb-1 | INFO: Started @1389ms
docker-jitsi-meet-stable-6826-jvb-1 | Jan 25, 2022 2:32:46 AM org.jitsi.utils.logging2.LoggerImpl log
docker-jitsi-meet-stable-6826-jvb-1 | WARNING: Cannot set presence extension: not connected.
docker-jitsi-meet-stable-6826-jvb-1 | Jan 25, 2022 2:32:51 AM org.jitsi.utils.logging2.LoggerImpl log
docker-jitsi-meet-stable-6826-jvb-1 | INFO: Performed a successful health check in PT0.000884S. Sticky failure: false
docker-jitsi-meet-stable-6826-jvb-1 | Jan 25, 2022 2:32:51 AM org.jitsi.utils.logging2.LoggerImpl log
docker-jitsi-meet-stable-6826-jvb-1 | WARNING: Cannot set presence extension: not connected.
docker-jitsi-meet-stable-6826-jvb-1 | Jan 25, 2022 2:32:56 AM org.jitsi.utils.logging2.LoggerImpl log
docker-jitsi-meet-stable-6826-jvb-1 | WARNING: Cannot set presence extension: not connected.
docker-jitsi-meet-stable-6826-jvb-1 | Jan 25, 2022 2:33:01 AM org.jitsi.utils.logging2.LoggerImpl log
docker-jitsi-meet-stable-6826-jvb-1 | INFO: Performed a successful health check in PT0.000014S. Sticky failure: false
docker-jitsi-meet-stable-6826-jvb-1 | Jan 25, 2022 2:33:01 AM org.jitsi.utils.logging2.LoggerImpl log
docker-jitsi-meet-stable-6826-jvb-1 | WARNING: Cannot set presence extension: not connected.
When I navigate to https://localhost:8443 in Firefox I get An error occurred during a connection to localhost:8443. PR_END_OF_FILE_ERROR.
docker-compose logs do not update immediately. But now they say:
docker-jitsi-meet-stable-6826-jicofo-1 | Jan 25, 2022 2:36:07 AM org.jitsi.utils.logging2.LoggerImpl log
docker-jitsi-meet-stable-6826-jicofo-1 | SEVERE: Failed to connect/login: The following addresses failed: 'RFC 6120 A/AAAA Endpoint + [xmpp.meet.jitsi:5222] (xmpp.meet.jitsi/172.21.0.2:5222)' failed because: java.net.SocketTimeoutException: connect timed out
docker-jitsi-meet-stable-6826-jicofo-1 | org.jivesoftware.smack.SmackException$EndpointConnectionException: The following addresses failed: 'RFC 6120 A/AAAA Endpoint + [xmpp.meet.jitsi:5222] (xmpp.meet.jitsi/172.21.0.2:5222)' failed because: java.net.SocketTimeoutException: connect timed out
docker-jitsi-meet-stable-6826-jicofo-1 | at org.jivesoftware.smack.SmackException$EndpointConnectionException.from(SmackException.java:334)
docker-jitsi-meet-stable-6826-jicofo-1 | at org.jivesoftware.smack.tcp.XMPPTCPConnection.connectUsingConfiguration(XMPPTCPConnection.java:663)
docker-jitsi-meet-stable-6826-jicofo-1 | at org.jivesoftware.smack.tcp.XMPPTCPConnection.connectInternal(XMPPTCPConnection.java:846)
docker-jitsi-meet-stable-6826-jicofo-1 | at org.jivesoftware.smack.AbstractXMPPConnection.connect(AbstractXMPPConnection.java:529)
docker-jitsi-meet-stable-6826-jicofo-1 | at org.jitsi.impl.protocol.xmpp.XmppProviderImpl.doConnect(XmppProviderImpl.java:205)
docker-jitsi-meet-stable-6826-jicofo-1 | at org.jitsi.retry.RetryStrategy$TaskRunner.run(RetryStrategy.java:167)
docker-jitsi-meet-stable-6826-jicofo-1 | at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
docker-jitsi-meet-stable-6826-jicofo-1 | at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
docker-jitsi-meet-stable-6826-jicofo-1 | at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
docker-jitsi-meet-stable-6826-jicofo-1 | at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
docker-jitsi-meet-stable-6826-jicofo-1 | at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
docker-jitsi-meet-stable-6826-jicofo-1 | at java.base/java.lang.Thread.run(Thread.java:829)
docker-jitsi-meet-stable-6826-jicofo-1 |
docker-jitsi-meet-stable-6826-jvb-1 | Jan 25, 2022 2:36:07 AM org.jitsi.utils.logging2.LoggerImpl log
docker-jitsi-meet-stable-6826-jvb-1 | WARNING: [MucClient id=shard hostname=xmpp.meet.jitsi] error connecting
docker-jitsi-meet-stable-6826-jvb-1 | org.jivesoftware.smack.SmackException$EndpointConnectionException: The following addresses failed: 'RFC 6120 A/AAAA Endpoint + [xmpp.meet.jitsi:5222] (xmpp.meet.jitsi/172.21.0.2:5222)' failed because: java.net.SocketTimeoutException: connect timed out
docker-jitsi-meet-stable-6826-jvb-1 | at org.jivesoftware.smack.SmackException$EndpointConnectionException.from(SmackException.java:334)
docker-jitsi-meet-stable-6826-jvb-1 | at org.jivesoftware.smack.tcp.XMPPTCPConnection.connectUsingConfiguration(XMPPTCPConnection.java:663)
docker-jitsi-meet-stable-6826-jvb-1 | at org.jivesoftware.smack.tcp.XMPPTCPConnection.connectInternal(XMPPTCPConnection.java:846)
docker-jitsi-meet-stable-6826-jvb-1 | at org.jivesoftware.smack.AbstractXMPPConnection.connect(AbstractXMPPConnection.java:529)
docker-jitsi-meet-stable-6826-jvb-1 | at org.jitsi.xmpp.mucclient.MucClient.lambda$getConnectAndLoginCallable$7(MucClient.java:613)
docker-jitsi-meet-stable-6826-jvb-1 | at org.jitsi.retry.RetryStrategy$TaskRunner.run(RetryStrategy.java:167)
docker-jitsi-meet-stable-6826-jvb-1 | at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
docker-jitsi-meet-stable-6826-jvb-1 | at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
docker-jitsi-meet-stable-6826-jvb-1 | at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
docker-jitsi-meet-stable-6826-jvb-1 | at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
docker-jitsi-meet-stable-6826-jvb-1 | at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
docker-jitsi-meet-stable-6826-jvb-1 | at java.base/java.lang.Thread.run(Thread.java:829)
docker-jitsi-meet-stable-6826-jvb-1 |
docker-jitsi-meet-stable-6826-jvb-1 | Jan 25, 2022 2:36:11 AM org.jitsi.utils.logging2.LoggerImpl log
docker-jitsi-meet-stable-6826-jvb-1 | INFO: Performed a successful health check in PT0.000008S. Sticky failure: false
docker-jitsi-meet-stable-6826-jvb-1 | Jan 25, 2022 2:36:11 AM org.jitsi.utils.logging2.LoggerImpl log
docker-jitsi-meet-stable-6826-jvb-1 | WARNING: Cannot set presence extension: not connected.
docker-jitsi-meet-stable-6826-jvb-1 | Jan 25, 2022 2:36:16 AM org.jitsi.utils.logging2.LoggerImpl log
docker-jitsi-meet-stable-6826-jvb-1 | WARNING: Cannot set presence extension: not connected.
docker-jitsi-meet-stable-6826-jvb-1 | Jan 25, 2022 2:36:21 AM org.jitsi.utils.logging2.LoggerImpl log
docker-jitsi-meet-stable-6826-jvb-1 | INFO: Performed a successful health check in PT0.000009S. Sticky failure: false
docker-jitsi-meet-stable-6826-jvb-1 | Jan 25, 2022 2:36:21 AM org.jitsi.utils.logging2.LoggerImpl log
docker-jitsi-meet-stable-6826-jvb-1 | WARNING: Cannot set presence extension: not connected.
docker-jitsi-meet-stable-6826-jvb-1 | Jan 25, 2022 2:36:26 AM org.jitsi.utils.logging2.LoggerImpl log
docker-jitsi-meet-stable-6826-jvb-1 | WARNING: Cannot set presence extension: not connected.
docker-jitsi-meet-stable-6826-jvb-1 | Jan 25, 2022 2:36:31 AM org.jitsi.utils.logging2.LoggerImpl log
docker-jitsi-meet-stable-6826-jvb-1 | INFO: Performed a successful health check in PT0.000008S. Sticky failure: false
docker-jitsi-meet-stable-6826-jvb-1 | Jan 25, 2022 2:36:31 AM org.jitsi.utils.logging2.LoggerImpl log
docker-jitsi-meet-stable-6826-jvb-1 | WARNING: Cannot set presence extension: not connected.
Do you have any firewall or something of the sort on your host machine?
I'm connected to a wireguard VPN, but it doesn't restrict any outbound connections. I don't have any firewall that I know of.
That'd odd it looks as if one container cannot reach the other. Can you please share your container logs?
i am having the same problem, did you manage to fix it??
No, it's broken. Cannot use.
Please share your container logs, we cannot help you otherwise.
Container logs are in my first post.
That's not all the containers. What about prosody?
Complete logs:
Attaching to docker-jitsi-meet-stable-6826-jicofo-1, docker-jitsi-meet-stable-6826-jvb-1, docker-jitsi-meet-stable-6826-prosody-1, docker-jitsi-meet-stable-6826-web-1
docker-jitsi-meet-stable-6826-prosody-1 | [s6-init] making user provided files available at /var/run/s6/etc...exited 0.
docker-jitsi-meet-stable-6826-web-1 | [s6-init] making user provided files available at /var/run/s6/etc...exited 0.
docker-jitsi-meet-stable-6826-prosody-1 | [s6-init] ensuring user provided files have correct perms...exited 0.
docker-jitsi-meet-stable-6826-web-1 | [s6-init] ensuring user provided files have correct perms...exited 0.
docker-jitsi-meet-stable-6826-prosody-1 | [fix-attrs.d] applying ownership & permissions fixes...
docker-jitsi-meet-stable-6826-web-1 | [fix-attrs.d] applying ownership & permissions fixes...
docker-jitsi-meet-stable-6826-prosody-1 | [fix-attrs.d] done.
docker-jitsi-meet-stable-6826-web-1 | [fix-attrs.d] done.
docker-jitsi-meet-stable-6826-web-1 | [cont-init.d] executing container initialization scripts...
docker-jitsi-meet-stable-6826-prosody-1 | [cont-init.d] executing container initialization scripts...
docker-jitsi-meet-stable-6826-web-1 | [cont-init.d] 01-set-timezone: executing...
docker-jitsi-meet-stable-6826-prosody-1 | [cont-init.d] 01-set-timezone: executing...
docker-jitsi-meet-stable-6826-web-1 | [cont-init.d] 01-set-timezone: exited 0.
docker-jitsi-meet-stable-6826-prosody-1 | [cont-init.d] 01-set-timezone: exited 0.
docker-jitsi-meet-stable-6826-web-1 | [cont-init.d] 10-config: executing...
docker-jitsi-meet-stable-6826-prosody-1 | [cont-init.d] 10-config: executing...
docker-jitsi-meet-stable-6826-web-1 | using keys found in /config/keys
docker-jitsi-meet-stable-6826-web-1 | [cont-init.d] 10-config: exited 0.
docker-jitsi-meet-stable-6826-web-1 | [cont-init.d] done.
docker-jitsi-meet-stable-6826-web-1 | [services.d] starting services
docker-jitsi-meet-stable-6826-web-1 | [services.d] done.
docker-jitsi-meet-stable-6826-prosody-1 | Adding user `prosody' to group `sasl' ...
docker-jitsi-meet-stable-6826-prosody-1 | Adding user prosody to group sasl
docker-jitsi-meet-stable-6826-prosody-1 | Done.
docker-jitsi-meet-stable-6826-prosody-1 | mv: cannot stat '/config/data/*.crt': No such file or directory
docker-jitsi-meet-stable-6826-prosody-1 | mv: cannot stat '/config/data/*.key': No such file or directory
docker-jitsi-meet-stable-6826-prosody-1 | [cont-init.d] 10-config: exited 0.
docker-jitsi-meet-stable-6826-prosody-1 | [cont-init.d] done.
docker-jitsi-meet-stable-6826-prosody-1 | [services.d] starting services
docker-jitsi-meet-stable-6826-prosody-1 | [services.d] done.
docker-jitsi-meet-stable-6826-prosody-1 | startup [1minfo[0m Hello and welcome to Prosody version 0.11.12
docker-jitsi-meet-stable-6826-prosody-1 | saslauthd[243] :num_procs : 5
docker-jitsi-meet-stable-6826-prosody-1 | saslauthd[243] :mech_option: /etc/saslauthd.conf
docker-jitsi-meet-stable-6826-prosody-1 | saslauthd[243] :run_path : /var/run/saslauthd
docker-jitsi-meet-stable-6826-prosody-1 | saslauthd[243] :auth_mech : ldap
docker-jitsi-meet-stable-6826-prosody-1 | saslauthd[243] :mmaped shared memory segment on file: /var/run/saslauthd/cache.mmap
docker-jitsi-meet-stable-6826-prosody-1 | saslauthd[243] :bucket size: 96 bytes
docker-jitsi-meet-stable-6826-prosody-1 | saslauthd[243] :stats size : 36 bytes
docker-jitsi-meet-stable-6826-prosody-1 | saslauthd[243] :timeout : 28800 seconds
docker-jitsi-meet-stable-6826-prosody-1 | saslauthd[243] :cache table: 985828 total bytes
docker-jitsi-meet-stable-6826-prosody-1 | saslauthd[243] :cache table: 1711 slots
docker-jitsi-meet-stable-6826-prosody-1 | saslauthd[243] :cache table: 10266 buckets
docker-jitsi-meet-stable-6826-prosody-1 | saslauthd[243] :flock file opened at /var/run/saslauthd/cache.flock
docker-jitsi-meet-stable-6826-prosody-1 | saslauthd[243] :using accept lock file: /var/run/saslauthd/mux.accept
docker-jitsi-meet-stable-6826-prosody-1 | saslauthd[243] :master pid is: 0
docker-jitsi-meet-stable-6826-prosody-1 | saslauthd[243] :listening on socket: /var/run/saslauthd/mux
docker-jitsi-meet-stable-6826-prosody-1 | saslauthd[243] :using process model
docker-jitsi-meet-stable-6826-prosody-1 | saslauthd[243] :forked child: 261
docker-jitsi-meet-stable-6826-prosody-1 | saslauthd[261] :acquired accept lock
docker-jitsi-meet-stable-6826-prosody-1 | saslauthd[243] :forked child: 262
docker-jitsi-meet-stable-6826-prosody-1 | saslauthd[243] :forked child: 263
docker-jitsi-meet-stable-6826-prosody-1 | saslauthd[243] :forked child: 264
docker-jitsi-meet-stable-6826-prosody-1 | startup [1minfo[0m Prosody is using the epoll backend for connection handling
docker-jitsi-meet-stable-6826-prosody-1 | meet.jitsi:tls [1minfo[0m Certificates loaded
docker-jitsi-meet-stable-6826-prosody-1 | portmanager [1minfo[0m Activated service 'c2s' on [*]:5222, [::]:5222
docker-jitsi-meet-stable-6826-prosody-1 | portmanager [1minfo[0m Activated service 'legacy_ssl' on no ports
docker-jitsi-meet-stable-6826-prosody-1 | portmanager [1minfo[0m Activated service 'http' on [*]:5280, [::]:5280
docker-jitsi-meet-stable-6826-prosody-1 | portmanager [1minfo[0m Activated service 'https' on no ports
docker-jitsi-meet-stable-6826-prosody-1 | lobby.meet.jitsi:tls [1minfo[0m Certificates loaded
docker-jitsi-meet-stable-6826-prosody-1 | meet.jitsi:muc_lobby_rooms [1minfo[0m Lobby component loaded lobby.meet.jitsi
docker-jitsi-meet-stable-6826-prosody-1 | internal-muc.meet.jitsi:tls [1minfo[0m Certificates loaded
docker-jitsi-meet-stable-6826-prosody-1 | focus.meet.jitsi:tls [1minfo[0m Certificates loaded
docker-jitsi-meet-stable-6826-prosody-1 | avmoderation.meet.jitsi:av_moderation_component [1minfo[0m Starting av_moderation for muc.meet.jitsi
docker-jitsi-meet-stable-6826-prosody-1 | avmoderation.meet.jitsi:av_moderation_component [1minfo[0m No muc component found, will listen for it: muc.meet.jitsi
docker-jitsi-meet-stable-6826-prosody-1 | avmoderation.meet.jitsi:tls [1minfo[0m Certificates loaded
docker-jitsi-meet-stable-6826-prosody-1 | avmoderation.meet.jitsi:av_moderation_component [1minfo[0m Hook to muc events on muc.meet.jitsi
docker-jitsi-meet-stable-6826-prosody-1 | meet.jitsi:muc_breakout_rooms [1minfo[0m Hook to muc events on muc.meet.jitsi
docker-jitsi-meet-stable-6826-prosody-1 | muc.meet.jitsi:tls [1minfo[0m Certificates loaded
docker-jitsi-meet-stable-6826-prosody-1 | meet.jitsi:muc_breakout_rooms [1minfo[0m Breakout rooms component created breakout.meet.jitsi
docker-jitsi-meet-stable-6826-prosody-1 | meet.jitsi:muc_breakout_rooms [1minfo[0m Hook to muc events on breakout.meet.jitsi
docker-jitsi-meet-stable-6826-prosody-1 | breakout.meet.jitsi:tls [1minfo[0m Certificates loaded
docker-jitsi-meet-stable-6826-prosody-1 | general [1minfo[0m Starting conference duration timer for muc.meet.jitsi
docker-jitsi-meet-stable-6826-prosody-1 | conferenceduration.meet.jitsi:conference_duration_component [1minfo[0m Hook to muc events on muc.meet.jitsi
docker-jitsi-meet-stable-6826-prosody-1 | conferenceduration.meet.jitsi:tls [1minfo[0m Certificates loaded
docker-jitsi-meet-stable-6826-prosody-1 | recorder.meet.jitsi:tls [1minfo[0m Certificates loaded
docker-jitsi-meet-stable-6826-prosody-1 | general [1minfo[0m Starting speakerstats for muc.meet.jitsi
docker-jitsi-meet-stable-6826-prosody-1 | speakerstats.meet.jitsi:speakerstats_component [1minfo[0m Hook to muc events on muc.meet.jitsi
docker-jitsi-meet-stable-6826-prosody-1 | speakerstats.meet.jitsi:tls [1minfo[0m Certificates loaded
docker-jitsi-meet-stable-6826-prosody-1 | auth.meet.jitsi:tls [1minfo[0m Certificates loaded
docker-jitsi-meet-stable-6826-jicofo-1 | [s6-init] making user provided files available at /var/run/s6/etc...exited 0.
docker-jitsi-meet-stable-6826-jvb-1 | [s6-init] making user provided files available at /var/run/s6/etc...exited 0.
docker-jitsi-meet-stable-6826-jicofo-1 | [s6-init] ensuring user provided files have correct perms...exited 0.
docker-jitsi-meet-stable-6826-jvb-1 | [s6-init] ensuring user provided files have correct perms...exited 0.
docker-jitsi-meet-stable-6826-jicofo-1 | [fix-attrs.d] applying ownership & permissions fixes...
docker-jitsi-meet-stable-6826-jvb-1 | [fix-attrs.d] applying ownership & permissions fixes...
docker-jitsi-meet-stable-6826-jvb-1 | [fix-attrs.d] done.
docker-jitsi-meet-stable-6826-jicofo-1 | [fix-attrs.d] done.
docker-jitsi-meet-stable-6826-jvb-1 | [cont-init.d] executing container initialization scripts...
docker-jitsi-meet-stable-6826-jicofo-1 | [cont-init.d] executing container initialization scripts...
docker-jitsi-meet-stable-6826-jicofo-1 | [cont-init.d] 01-set-timezone: executing...
docker-jitsi-meet-stable-6826-jvb-1 | [cont-init.d] 01-set-timezone: executing...
docker-jitsi-meet-stable-6826-jvb-1 | [cont-init.d] 01-set-timezone: exited 0.
docker-jitsi-meet-stable-6826-jicofo-1 | [cont-init.d] 01-set-timezone: exited 0.
docker-jitsi-meet-stable-6826-jvb-1 | [cont-init.d] 10-config: executing...
docker-jitsi-meet-stable-6826-jicofo-1 | [cont-init.d] 10-config: executing...
docker-jitsi-meet-stable-6826-jicofo-1 | [cont-init.d] 10-config: exited 0.
docker-jitsi-meet-stable-6826-jicofo-1 | [cont-init.d] done.
docker-jitsi-meet-stable-6826-jicofo-1 | [services.d] starting services
docker-jitsi-meet-stable-6826-jicofo-1 | [services.d] done.
docker-jitsi-meet-stable-6826-jvb-1 | [cont-init.d] 10-config: exited 0.
docker-jitsi-meet-stable-6826-jvb-1 | [cont-init.d] done.
docker-jitsi-meet-stable-6826-jvb-1 | [services.d] starting services
docker-jitsi-meet-stable-6826-jvb-1 | [services.d] done.
docker-jitsi-meet-stable-6826-jicofo-1 | Feb 07, 2022 6:11:10 PM org.jitsi.utils.logging2.LoggerImpl log
docker-jitsi-meet-stable-6826-jicofo-1 | INFO: Starting Jicofo.
docker-jitsi-meet-stable-6826-jicofo-1 | Feb 07, 2022 6:11:10 PM org.jitsi.utils.logging2.LoggerImpl log
docker-jitsi-meet-stable-6826-jicofo-1 | INFO: Initialized newConfig: merge of /config/jicofo.conf: 1,system properties,reference.conf @ jar:file:/usr/share/jicofo/jicofo.jar!/reference.conf: 1
docker-jitsi-meet-stable-6826-jicofo-1 | Feb 07, 2022 6:11:10 PM org.jitsi.utils.logging2.LoggerImpl log
docker-jitsi-meet-stable-6826-jicofo-1 | INFO: net.java.sip.communicator.SC_HOME_DIR_LOCATION not set
docker-jitsi-meet-stable-6826-jicofo-1 | Feb 07, 2022 6:11:10 PM org.jitsi.utils.logging2.LoggerImpl log
docker-jitsi-meet-stable-6826-jicofo-1 | INFO: Initialized legacyConfig: sip communicator props (no description provided)
docker-jitsi-meet-stable-6826-jicofo-1 | Feb 07, 2022 6:11:10 PM org.jitsi.utils.logging2.LoggerImpl log
docker-jitsi-meet-stable-6826-jicofo-1 | INFO: Reloading the Typesafe config source (previously reloaded 0 times).
docker-jitsi-meet-stable-6826-jvb-1 | Feb 07, 2022 6:11:10 PM org.jitsi.utils.logging2.LoggerImpl log
docker-jitsi-meet-stable-6826-jvb-1 | INFO: Initialized newConfig: merge of /config/jvb.conf: 1,application.conf @ jar:file:/usr/share/jitsi-videobridge/jitsi-videobridge.jar!/application.conf: 1,system properties,reference.conf @ jar:file:/usr/share/jitsi-videobridge/jitsi-videobridge.jar!/reference.conf: 1,reference.conf @ jar:file:/usr/share/jitsi-videobridge/lib/ice4j-3.0-46-g64a7ca8.jar!/reference.conf: 1,reference.conf @ jar:file:/usr/share/jitsi-videobridge/lib/jitsi-media-transform-1.0-276-gf95fb9d.jar!/reference.conf: 1
docker-jitsi-meet-stable-6826-jvb-1 | Feb 07, 2022 6:11:10 PM org.jitsi.utils.logging2.LoggerImpl log
docker-jitsi-meet-stable-6826-jvb-1 | INFO: loading config file at path /config/sip-communicator.properties
docker-jitsi-meet-stable-6826-jvb-1 | Feb 07, 2022 6:11:10 PM org.jitsi.utils.logging2.LoggerImpl log
docker-jitsi-meet-stable-6826-jvb-1 | INFO: Error loading config file: java.io.FileNotFoundException: /config/sip-communicator.properties (No such file or directory)
docker-jitsi-meet-stable-6826-jvb-1 | Feb 07, 2022 6:11:10 PM org.jitsi.utils.logging2.LoggerImpl log
docker-jitsi-meet-stable-6826-jvb-1 | INFO: Initialized legacyConfig: sip communicator props (no description provided)
docker-jitsi-meet-stable-6826-jvb-1 | Feb 07, 2022 6:11:10 PM org.jitsi.utils.logging2.LoggerImpl log
docker-jitsi-meet-stable-6826-jvb-1 | INFO: Reloading the Typesafe config source (previously reloaded 0 times).
docker-jitsi-meet-stable-6826-jvb-1 | Feb 07, 2022 6:11:10 PM org.jitsi.utils.logging2.LoggerImpl log
docker-jitsi-meet-stable-6826-jvb-1 | INFO: Starting jitsi-videobridge version 2.1.607-g153f7e4e
docker-jitsi-meet-stable-6826-jvb-1 | Feb 07, 2022 6:11:10 PM org.ice4j.ice.harvest.MappingCandidateHarvesters initialize
docker-jitsi-meet-stable-6826-jvb-1 | INFO: Using AwsCandidateHarvester.
docker-jitsi-meet-stable-6826-jicofo-1 | Feb 07, 2022 6:11:11 PM org.jitsi.utils.logging2.LoggerImpl log
docker-jitsi-meet-stable-6826-jicofo-1 | INFO: Initialized octoId=1
docker-jitsi-meet-stable-6826-jicofo-1 | Feb 07, 2022 6:11:11 PM org.jitsi.utils.logging2.LoggerImpl log
docker-jitsi-meet-stable-6826-jicofo-1 | INFO: Authentication service disabled.
docker-jitsi-meet-stable-6826-jvb-1 | Feb 07, 2022 6:11:11 PM org.jitsi.utils.logging2.LoggerImpl log
docker-jitsi-meet-stable-6826-jvb-1 | INFO: Initializing a new MucClient for [ org.jitsi.xmpp.mucclient.MucClientConfiguration id=shard domain=auth.meet.jitsi hostname=xmpp.meet.jitsi port=null username=jvb mucs=[[email protected]] mucNickname=878766011bda disableCertificateVerification=true]
docker-jitsi-meet-stable-6826-jvb-1 | Feb 07, 2022 6:11:11 PM org.jitsi.utils.logging2.LoggerImpl log
docker-jitsi-meet-stable-6826-jvb-1 | WARNING: Disabling certificate verification!
docker-jitsi-meet-stable-6826-jvb-1 | Feb 07, 2022 6:11:11 PM org.jitsi.utils.logging2.LoggerImpl log
docker-jitsi-meet-stable-6826-jvb-1 | INFO: LastNReducer with reductionScale: 0.75 recoverScale: 1.25 impactTime: PT1M minLastN: 1 maxEnforcedLastN: 40
docker-jitsi-meet-stable-6826-jvb-1 | Feb 07, 2022 6:11:11 PM org.jitsi.utils.logging2.LoggerImpl log
docker-jitsi-meet-stable-6826-jvb-1 | INFO: TaskPools detected 32 processors, creating the CPU pool with that many threads
docker-jitsi-meet-stable-6826-jicofo-1 | Feb 07, 2022 6:11:11 PM org.jitsi.utils.logging2.LoggerImpl log
docker-jitsi-meet-stable-6826-jicofo-1 | WARNING: Disabling TLS certificate verification!
docker-jitsi-meet-stable-6826-jvb-1 | Feb 07, 2022 6:11:11 PM org.jitsi.utils.logging2.LoggerImpl log
docker-jitsi-meet-stable-6826-jvb-1 | WARNING: Running with open files limit 1048576 (hard 1048576), thread limit null (hard null). These values are too low and they will limit the number of participants that the bridge can serve simultaneously.
docker-jitsi-meet-stable-6826-jvb-1 | Feb 07, 2022 6:11:11 PM org.jitsi.utils.logging2.LoggerImpl log
docker-jitsi-meet-stable-6826-jvb-1 | INFO: Starting with 60 second interval.
docker-jitsi-meet-stable-6826-jvb-1 | Feb 07, 2022 6:11:11 PM org.ice4j.ice.harvest.MappingCandidateHarvesters createStunHarvesters
docker-jitsi-meet-stable-6826-jvb-1 | INFO: Using 152.67.119.104:443/udp for StunMappingCandidateHarvester (localAddress=172.21.0.4:0/udp).
docker-jitsi-meet-stable-6826-jvb-1 | Feb 07, 2022 6:11:11 PM org.jitsi.utils.logging2.LoggerImpl log
docker-jitsi-meet-stable-6826-jvb-1 | INFO: Started with interval=10000, timeout=PT30S, maxDuration=PT3S, stickyFailures=false.
docker-jitsi-meet-stable-6826-jvb-1 | Feb 07, 2022 6:11:11 PM org.jitsi.utils.logging2.LoggerImpl log
docker-jitsi-meet-stable-6826-jvb-1 | INFO: Not starting CallstatsService, disabled in configuration.
docker-jitsi-meet-stable-6826-jvb-1 | Feb 07, 2022 6:11:11 PM org.jitsi.utils.logging2.LoggerImpl log
docker-jitsi-meet-stable-6826-jvb-1 | INFO: Starting public http server
docker-jitsi-meet-stable-6826-jvb-1 | Feb 07, 2022 6:11:11 PM org.ice4j.ice.harvest.StunMappingCandidateHarvester discover
docker-jitsi-meet-stable-6826-jvb-1 | INFO: Discovered public address 89.44.10.68:49724/udp from STUN server 152.67.119.104:443/udp using local address org.ice4j.socket.IceUdpSocketWrapper@60f9191
docker-jitsi-meet-stable-6826-jicofo-1 | Feb 07, 2022 6:11:11 PM org.jitsi.utils.logging2.LoggerImpl log
docker-jitsi-meet-stable-6826-jicofo-1 | INFO: No dedicated Service XMPP connection configured, re-using the client XMPP connection.
docker-jitsi-meet-stable-6826-jvb-1 | Feb 07, 2022 6:11:11 PM org.jitsi.utils.logging2.LoggerImpl log
docker-jitsi-meet-stable-6826-jvb-1 | INFO: Dispatching a thread to connect and login.
docker-jitsi-meet-stable-6826-jicofo-1 | Feb 07, 2022 6:11:11 PM org.jitsi.utils.logging2.LoggerImpl log
docker-jitsi-meet-stable-6826-jicofo-1 | INFO: No Jigasi detector configured.
docker-jitsi-meet-stable-6826-jvb-1 | Feb 07, 2022 6:11:11 PM org.jitsi.utils.logging2.LoggerImpl log
docker-jitsi-meet-stable-6826-jvb-1 | INFO: Base URL: wss://localhost:8443/colibri-ws/172.21.0.4
docker-jitsi-meet-stable-6826-jicofo-1 | Feb 07, 2022 6:11:11 PM org.jitsi.utils.logging2.LoggerImpl log
docker-jitsi-meet-stable-6826-jicofo-1 | INFO: Using org.jitsi.jicofo.bridge.SingleBridgeSelectionStrategy
docker-jitsi-meet-stable-6826-jicofo-1 | Feb 07, 2022 6:11:11 PM org.jitsi.utils.logging2.LoggerImpl log
docker-jitsi-meet-stable-6826-jicofo-1 | INFO: Initialized with [email protected]
docker-jitsi-meet-stable-6826-jvb-1 | Feb 07, 2022 6:11:11 PM org.eclipse.jetty.util.log.Log initialized
docker-jitsi-meet-stable-6826-jvb-1 | INFO: Logging initialized @882ms to org.eclipse.jetty.util.log.JavaUtilLog
docker-jitsi-meet-stable-6826-jicofo-1 | Feb 07, 2022 6:11:11 PM org.jitsi.utils.logging2.LoggerImpl log
docker-jitsi-meet-stable-6826-jicofo-1 | INFO: No Jibri detector configured.
docker-jitsi-meet-stable-6826-jicofo-1 | Feb 07, 2022 6:11:11 PM org.jitsi.utils.logging2.LoggerImpl log
docker-jitsi-meet-stable-6826-jicofo-1 | INFO: No SIP Jibri detector configured.
docker-jitsi-meet-stable-6826-jicofo-1 | Feb 07, 2022 6:11:11 PM org.jitsi.utils.logging2.LoggerImpl log
docker-jitsi-meet-stable-6826-jicofo-1 | INFO: Starting HTTP server with config: host=null, port=8888, tlsPort=8843, isTls=false, keyStorePath=null, sendServerVersion=true.
docker-jitsi-meet-stable-6826-jvb-1 | Feb 07, 2022 6:11:11 PM org.jitsi.utils.logging2.LoggerImpl log
docker-jitsi-meet-stable-6826-jvb-1 | INFO: Registering servlet at /colibri-ws/*, baseUrl = wss://localhost:8443/colibri-ws/172.21.0.4
docker-jitsi-meet-stable-6826-jicofo-1 | Feb 07, 2022 6:11:11 PM org.eclipse.jetty.util.log.Log initialized
docker-jitsi-meet-stable-6826-jicofo-1 | INFO: Logging initialized @991ms to org.eclipse.jetty.util.log.Slf4jLog
docker-jitsi-meet-stable-6826-jvb-1 | Feb 07, 2022 6:11:11 PM org.eclipse.jetty.server.Server doStart
docker-jitsi-meet-stable-6826-jvb-1 | INFO: jetty-9.4.44.v20210927; built: 2021-09-27T23:02:44.612Z; git: 8da83308eeca865e495e53ef315a249d63ba9332; jvm 11.0.13+8-post-Debian-1deb11u1
docker-jitsi-meet-stable-6826-jvb-1 | Feb 07, 2022 6:11:11 PM org.eclipse.jetty.server.handler.ContextHandler doStart
docker-jitsi-meet-stable-6826-jvb-1 | INFO: Started o.e.j.s.ServletContextHandler@5bbc9f97{/,null,AVAILABLE}
docker-jitsi-meet-stable-6826-jvb-1 | Feb 07, 2022 6:11:11 PM org.eclipse.jetty.server.AbstractConnector doStart
docker-jitsi-meet-stable-6826-jvb-1 | INFO: Started ServerConnector@f19c9d2{HTTP/1.1, (http/1.1)}{0.0.0.0:9090}
docker-jitsi-meet-stable-6826-jvb-1 | Feb 07, 2022 6:11:11 PM org.eclipse.jetty.server.Server doStart
docker-jitsi-meet-stable-6826-jvb-1 | INFO: Started @980ms
docker-jitsi-meet-stable-6826-jvb-1 | Feb 07, 2022 6:11:11 PM org.jitsi.utils.logging2.LoggerImpl log
docker-jitsi-meet-stable-6826-jvb-1 | INFO: Starting private http server
docker-jitsi-meet-stable-6826-jicofo-1 | Feb 07, 2022 6:11:11 PM org.eclipse.jetty.server.Server doStart
docker-jitsi-meet-stable-6826-jicofo-1 | INFO: jetty-9.4.44.v20210927; built: 2021-09-27T23:02:44.612Z; git: 8da83308eeca865e495e53ef315a249d63ba9332; jvm 11.0.13+8-post-Debian-1deb11u1
docker-jitsi-meet-stable-6826-jvb-1 | Feb 07, 2022 6:11:11 PM org.eclipse.jetty.server.Server doStart
docker-jitsi-meet-stable-6826-jvb-1 | INFO: jetty-9.4.44.v20210927; built: 2021-09-27T23:02:44.612Z; git: 8da83308eeca865e495e53ef315a249d63ba9332; jvm 11.0.13+8-post-Debian-1deb11u1
docker-jitsi-meet-stable-6826-jvb-1 | Feb 07, 2022 6:11:11 PM org.glassfish.jersey.server.wadl.WadlFeature configure
docker-jitsi-meet-stable-6826-jvb-1 | WARNING: JAXBContext implementation could not be found. WADL feature is disabled.
docker-jitsi-meet-stable-6826-jicofo-1 | Feb 07, 2022 6:11:11 PM org.glassfish.jersey.server.wadl.WadlFeature configure
docker-jitsi-meet-stable-6826-jicofo-1 | WARNING: JAXBContext implementation could not be found. WADL feature is disabled.
docker-jitsi-meet-stable-6826-jvb-1 | Feb 07, 2022 6:11:11 PM org.glassfish.jersey.internal.inject.Providers checkProviderRuntime
docker-jitsi-meet-stable-6826-jvb-1 | WARNING: A provider org.jitsi.rest.Health registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider org.jitsi.rest.Health will be ignored.
docker-jitsi-meet-stable-6826-jvb-1 | Feb 07, 2022 6:11:11 PM org.glassfish.jersey.internal.inject.Providers checkProviderRuntime
docker-jitsi-meet-stable-6826-jvb-1 | WARNING: A provider org.jitsi.rest.Version registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider org.jitsi.rest.Version will be ignored.
docker-jitsi-meet-stable-6826-jicofo-1 | Feb 07, 2022 6:11:11 PM org.glassfish.jersey.internal.inject.Providers checkProviderRuntime
docker-jitsi-meet-stable-6826-jicofo-1 | WARNING: A provider org.jitsi.rest.Version registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider org.jitsi.rest.Version will be ignored.
docker-jitsi-meet-stable-6826-jvb-1 | Feb 07, 2022 6:11:11 PM org.ice4j.ice.harvest.MappingCandidateHarvesters maybeAdd
docker-jitsi-meet-stable-6826-jvb-1 | INFO: Discarding a mapping harvester: org.ice4j.ice.harvest.AwsCandidateHarvester@42cdacae
docker-jitsi-meet-stable-6826-jvb-1 | Feb 07, 2022 6:11:11 PM org.ice4j.ice.harvest.MappingCandidateHarvesters initialize
docker-jitsi-meet-stable-6826-jvb-1 | INFO: Using org.ice4j.ice.harvest.StunMappingCandidateHarvester@c9276b0
docker-jitsi-meet-stable-6826-jvb-1 | Feb 07, 2022 6:11:11 PM org.ice4j.ice.harvest.MappingCandidateHarvesters initialize
docker-jitsi-meet-stable-6826-jvb-1 | INFO: Initialized mapping harvesters (delay=968ms). stunDiscoveryFailed=false
docker-jitsi-meet-stable-6826-jicofo-1 | Feb 07, 2022 6:11:11 PM org.eclipse.jetty.server.handler.ContextHandler doStart
docker-jitsi-meet-stable-6826-jicofo-1 | INFO: Started o.e.j.s.ServletContextHandler@57ddd45b{/,null,AVAILABLE}
docker-jitsi-meet-stable-6826-jicofo-1 | Feb 07, 2022 6:11:11 PM org.eclipse.jetty.server.AbstractConnector doStart
docker-jitsi-meet-stable-6826-jicofo-1 | INFO: Started ServerConnector@2bc9a775{HTTP/1.1, (http/1.1)}{0.0.0.0:8888}
docker-jitsi-meet-stable-6826-jicofo-1 | Feb 07, 2022 6:11:11 PM org.eclipse.jetty.server.Server doStart
docker-jitsi-meet-stable-6826-jicofo-1 | INFO: Started @1459ms
docker-jitsi-meet-stable-6826-jvb-1 | Feb 07, 2022 6:11:11 PM org.eclipse.jetty.server.handler.ContextHandler doStart
docker-jitsi-meet-stable-6826-jvb-1 | INFO: Started o.e.j.s.ServletContextHandler@31e76a8d{/,null,AVAILABLE}
docker-jitsi-meet-stable-6826-jvb-1 | Feb 07, 2022 6:11:11 PM org.eclipse.jetty.server.AbstractConnector doStart
docker-jitsi-meet-stable-6826-jvb-1 | INFO: Started ServerConnector@30f4b1a6{HTTP/1.1, (http/1.1)}{0.0.0.0:8080}
docker-jitsi-meet-stable-6826-jvb-1 | Feb 07, 2022 6:11:11 PM org.eclipse.jetty.server.Server doStart
docker-jitsi-meet-stable-6826-jvb-1 | INFO: Started @1427ms
docker-jitsi-meet-stable-6826-jvb-1 | Feb 07, 2022 6:11:16 PM org.jitsi.utils.logging2.LoggerImpl log
docker-jitsi-meet-stable-6826-jvb-1 | WARNING: Cannot set presence extension: not connected.
docker-jitsi-meet-stable-6826-jvb-1 | Feb 07, 2022 6:11:21 PM org.jitsi.utils.logging2.LoggerImpl log
docker-jitsi-meet-stable-6826-jvb-1 | INFO: Performed a successful health check in PT0.000776S. Sticky failure: false
docker-jitsi-meet-stable-6826-jvb-1 | Feb 07, 2022 6:11:21 PM org.jitsi.utils.logging2.LoggerImpl log
docker-jitsi-meet-stable-6826-jvb-1 | WARNING: Cannot set presence extension: not connected.
docker-jitsi-meet-stable-6826-jvb-1 | Feb 07, 2022 6:11:26 PM org.jitsi.utils.logging2.LoggerImpl log
docker-jitsi-meet-stable-6826-jvb-1 | WARNING: Cannot set presence extension: not connected.
But then on this one I see no error (unless GH for mobile cropped the comment.
When do you see the error, when starting a meeting or earlier?
What do you see in the JS console in the browser?
But then on this one I see no error (unless GH for mobile cropped the comment.
When do you see the error, when starting a meeting or earlier?
What do you see in the JS console in the browser?
Please read the original issue. I cannot even navigate to the page, much less start a meeting.
Can you follow the official instructions and reproduce the error?
I cannot reproduce the error myself, that's why I'm trying to understand where to start looking.
Hi @saghul , I'm facing the exact same issue. Here are the logs:
Jibri 2022-04-14 12:49:54.435 INFO: [1] XmppApi.start#156: Connecting to xmpp environment on spaces.mydomain.one with config XmppEnvironmentConfig(name=<no value>, xmppServerHosts=[spaces.mydomain.one], xmppDomain=spaces.mydomain.one, baseUrl=https://spaces.mydomain.one, controlLogin=XmppCredentials(domain=auth.spaces.mydomain.one, port=null, username=jibri, password=*****), controlMuc=XmppMuc(domain=internal.auth.spaces.mydomain.one, roomName=jibribrewery, nickname=jibri-338329852), sipControlMuc=null, callLogin=XmppCredentials(domain=recorder.spaces.mydomain.one, port=null, username=recorder, password=*****), stripFromRoomDomain=conference., usageTimeoutMins=0, trustAllXmppCerts=true, securityMode=null) Jibri 2022-04-14 12:49:54.436 INFO: [1] XmppApi.start#168: The trustAllXmppCerts config is enabled for this domain, all XMPP server provided certificates will be accepted Jibri 2022-04-14 12:49:54.467 FINE: [1] MainKt$setupMetaconfigLogger$1.debug#232: FallbackSupplier: checking for value via suppliers: ConfigSourceSupplier: key: 'http_api_port', type: 'kotlin.Int', source: 'command line args' ConfigSourceSupplier: key: 'jibri.api.http.external-api-port', type: 'kotlin.Int', source: 'config' Jibri 2022-04-14 12:49:54.470 INFO: [31] [hostname=spaces.mydomain.one id=spaces.mydomain.one] MucClient.initializeConnectAndJoin#278: Initializing a new MucClient for [ org.jitsi.xmpp.mucclient.MucClientConfiguration id=spaces.mydomain.one domain=auth.spaces.mydomain.one hostname=spaces.mydomain.one port=null username=jibri mucs=[[email protected]] mucNickname=jibri-338329852 disableCertificateVerification=true] Jibri 2022-04-14 12:49:54.471 FINE: [1] MainKt$setupMetaconfigLogger$1.debug#232: ConfigSourceSupplier: Trying to retrieve key 'http_api_port' from source 'command line args' as type kotlin.Int Jibri 2022-04-14 12:49:54.471 FINE: [1] MainKt$setupMetaconfigLogger$1.debug#232: FallbackSupplier: failed to find value via ConfigSourceSupplier: key: 'http_api_port', type: 'kotlin.Int', source: 'command line args': org.jitsi.metaconfig.ConfigException$UnableToRetrieve$NotFound: not found Jibri 2022-04-14 12:49:54.472 FINE: [1] MainKt$setupMetaconfigLogger$1.debug#232: ConfigSourceSupplier: Trying to retrieve key 'jibri.api.http.external-api-port' from source 'config' as type kotlin.Int Jibri 2022-04-14 12:49:54.472 FINE: [1] MainKt$setupMetaconfigLogger$1.debug#232: ConfigSourceSupplier: Successfully retrieved key 'jibri.api.http.external-api-port' from source 'config' as type kotlin.Int Jibri 2022-04-14 12:49:54.473 FINE: [1] MainKt$setupMetaconfigLogger$1.debug#232: FallbackSupplier: value found via ConfigSourceSupplier: key: 'jibri.api.http.external-api-port', type: 'kotlin.Int', source: 'config' Jibri 2022-04-14 12:49:54.473 INFO: [1] MainKt.main#152: Using port 2222 for HTTP API Jibri 2022-04-14 12:49:54.503 WARNING: [31] MucClient.createXMPPTCPConnectionConfiguration#116: Disabling certificate verification! Jibri 2022-04-14 12:49:54.554 INFO: [31] [hostname=spaces.mydomain.one id=spaces.mydomain.one] MucClient.initializeConnectAndJoin#340: Dispatching a thread to connect and login. Jibri 2022-04-14 12:50:24.548 WARNING: [30] org.jivesoftware.smackx.ping.PingManager.pingServerIfNecessary: XMPPTCPConnection[not-authenticated] (0) was not authenticated Jibri 2022-04-14 12:50:24.607 WARNING: [31] [hostname=spaces.mydomain.one id=spaces.mydomain.one] MucClient.lambda$getConnectAndLoginCallable$7#630: Error connecting: org.jivesoftware.smack.SmackException$EndpointConnectionException: The following addresses failed: 'RFC 6120 A/AAAA Endpoint + [spaces.mydomain.one:5222] (spaces.mydomain.one/127.0.0.1:5222)' failed because: java.net.ConnectException: Connection refused (Connection refused), 'RFC 6120 A/AAAA Endpoint + [spaces.mydomain.one:5222] (spaces.mydomain.one/3.108.251.52:5222)' failed because: java.net.SocketTimeoutException: connect timed out at org.jivesoftware.smack.SmackException$EndpointConnectionException.from(SmackException.java:334) at org.jivesoftware.smack.tcp.XMPPTCPConnection.connectUsingConfiguration(XMPPTCPConnection.java:664) at org.jivesoftware.smack.tcp.XMPPTCPConnection.connectInternal(XMPPTCPConnection.java:849) at org.jivesoftware.smack.AbstractXMPPConnection.connect(AbstractXMPPConnection.java:526) at org.jitsi.xmpp.mucclient.MucClient.lambda$getConnectAndLoginCallable$7(MucClient.java:625) at org.jitsi.retry.RetryStrategy$TaskRunner.run(RetryStrategy.java:167) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:829)
.env file content
`# JIBRI CONFIG
Public URL of your Jitsi
PUBLIC_URL=https://spaces.mydomain.one
Internal XMPP domain for authenticated services
XMPP_AUTH_DOMAIN=auth.spaces.mydomain.one
XMPP domain for the internal MUC used for jibri, jigasi and jvb pools
XMPP_INTERNAL_MUC_DOMAIN=internal.auth.spaces.mydomain.one
XMPP domain for the jibri recorder
XMPP_RECORDER_DOMAIN=recorder.spaces.mydomain.one
Internal XMPP server
XMPP_SERVER=spaces.mydomain.one
Internal XMPP domain
XMPP_DOMAIN=spaces.mydomain.one
XMPP user for Jibri client connections
JIBRI_XMPP_USER=jibri
XMPP password for Jibri client connections
JIBRI_XMPP_PASSWORD=Porsche911
MUC name for the Jibri pool
JIBRI_BREWERY_MUC=jibribrewery
XMPP recorder user for Jibri client connections
JIBRI_RECORDER_USER=recorder
XMPP recorder password for Jibri client connections
JIBRI_RECORDER_PASSWORD=Porsche911
Directory for recordings inside Jibri container
JIBRI_RECORDING_DIR=/config/recordings
The finalizing script. Will run after recording is complete
JIBRI_FINALIZE_RECORDING_SCRIPT_PATH=/config/finalize.sh
When jibri gets a request to start a service for a room, the room
jid will look like: [email protected]_domain
We'll build the url for the call by transforming that into:
https://xmpp_domain/subdomain/roomName
So if there are any prefixes in the jid (like jitsi meet, which
has its participants join a muc at conference.xmpp_domain) then
list that prefix here so it can be stripped out to generate
the call url correctly
JIBRI_STRIP_DOMAIN_JID=conference
Directory for logs inside Jibri container
JIBRI_LOGS_DIR=/config/logs DISPLAY=:0=`
jibri.yml :
- XMPP_RECORDER_DOMAIN - XMPP_SERVER - XMPP_DOMAIN - JIBRI_XMPP_USER - JIBRI_XMPP_PASSWORD - JIBRI_BREWERY_MUC - JIBRI_RECORDER_USER - JIBRI_RECORDER_PASSWORD - JIBRI_RECORDING_DIR - JIBRI_FINALIZE_RECORDING_SCRIPT_PATH - JIBRI_STRIP_DOMAIN_JID - JIBRI_LOGS_DIR - DISPLAY=:0 - TZ jibri6: image: jitsi/jibri restart: ${RESTART_POLICY} volumes: - ${CONFIG}/jibri6:/config:Z - /dev/shm:/dev/shm - /root/jibri-docker/config/.asoundrc6:/home/jibri/.asoundrc - /root/jibri-docker/recordings:/config/recordings - /root/jibri-docker/config/finalize.sh:/config/finalize.sh - /home/ubuntu:/home/jibri cap_add: - SYS_ADMIN - NET_BIND_SERVICE devices: - /dev/snd:/dev/snd environment: - PUBLIC_URL - XMPP_AUTH_DOMAIN - XMPP_INTERNAL_MUC_DOMAIN - XMPP_RECORDER_DOMAIN - XMPP_SERVER - XMPP_DOMAIN - JIBRI_XMPP_USER - JIBRI_XMPP_PASSWORD - JIBRI_BREWERY_MUC - JIBRI_RECORDER_USER - JIBRI_RECORDER_PASSWORD - JIBRI_RECORDING_DIR - JIBRI_FINALIZE_RECORDING_SCRIPT_PATH - JIBRI_STRIP_DOMAIN_JID - JIBRI_LOGS_DIR - DISPLAY=:0 - TZ
jicofo.conf :
jicofo { authentication: { enabled: true type: XMPP login-url: spaces.mydomain.one } xmpp: { client: { client-proxy: focus.spaces.mydomain.one } trusted-domains: [ "recorder.spaces.mydomain.one" ] } bridge: { brewery-jid: "[email protected]" } jibri: { brewery-jid: "[email protected]" pending-timeout: 90 seconds } }
prosody -> mydomain.cfg.lua
` admins = { "[email protected]", "[email protected]", "[email protected]" } muc_room_locking = false muc_room_default_public_jids = true muc_room_cache_size = 1000 c2s_require_encryption = false
VirtualHost "auth.spaces.mydomain.one" ssl = { key = "/etc/prosody/certs/auth.spaces.mydomain.one.key"; certificate = "/etc/prosody/certs/auth.spaces.mydomain.one.crt"; } modules_enabled = { "limits_exception"; } authentication = "internal_hashed"
VirtualHost "recorder.spaces.mydomain.one" modules_enabled = { "ping"; } authentication = "internal_plain" c2s_require_encryption = false allow_empty_token = true
-- Proxy to jicofo's user JID, so that it doesn't have to register as a component. Component "focus.spaces.mydomain.one" "client_proxy" target_address = "[email protected]"
Component "speakerstats.spaces.mydomain.one" "speakerstats_component" muc_component = "conference.spaces.mydomain.one"
Component "conferenceduration.spaces.mydomain.one" "conference_duration_component" muc_component = "conference.spaces.mydomain.one"
Component "avmoderation.spaces.mydomain.one" "av_moderation_component" muc_component = "conference.spaces.mydomain.one"
Component "lobby.spaces.mydomain.one" "muc" storage = "memory" restrict_room_creation = true muc_room_locking = false muc_room_default_public_jids = true modules_enabled = { "muc_rate_limit"; "polls"; } `
Any help is deeply appreciated.
@saghul and team, can anyone help me out with the above issue. I can provide more details if needed.
I don't think you are supposed to change "Internal XMPP domain" (https://jitsi.github.io/handbook/docs/devops-guide/devops-guide-docker/#advanced-configuration), but even without that I seem to have the same issue - I can curl localhost:80 on the server successfully, but connection is refused from the outside, in fact the request never arrives at the container...
