-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
vanilla install (ton of errors in docker logs) #439
Comments
What image versions are you running? can you please share your .env file? |
https://gist.github.com/chovy/b07f35a80345bec5529e7f37655b6b13 I'm using your docker compose file here: https://gist.github.com/chovy/4dde28f8dceb189c2766bfd5f1f437ec |
Did you pull the latest images? |
Seeing at least a few of those errors as well. I followed the steps here: What needs doin?! |
Similar here. On Docker installed on Windows as well as on Linux. Followed the steps according quick-start. prosody_1 | c2s55fcc7d239d0 info Client disconnected: connection closed
jvb_1 | Apr 19, 2020 6:04:57 PM org.jitsi.utils.logging2.LoggerImpl log
jvb_1 | INFO: Logging in.
jvb_1 | Apr 19, 2020 6:04:57 PM org.jitsi.utils.logging.LoggerImpl log
jvb_1 | SEVERE: org.jivesoftware.smack.sasl.SASLErrorException: SASLError using SCRAM-SHA-1: not-authorized
jvb_1 | org.jivesoftware.smack.sasl.SASLErrorException: SASLError using SCRAM-SHA-1: not-authorized
jvb_1 | at org.jivesoftware.smack.SASLAuthentication.authenticationFailed(SASLAuthentication.java:292)
jvb_1 | at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader.parsePackets(XMPPTCPConnection.java:1100)
jvb_1 | at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader.access$300(XMPPTCPConnection.java:1000)
jvb_1 | at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader$1.run(XMPPTCPConnection.java:1016)
jvb_1 | at java.lang.Thread.run(Thread.java:748)
jvb_1 |
prosody_1 | jcp55fcc7b9b730 info Incoming Jabber component connection
prosody_1 | focus.meet.jitsi:component info Component authentication failed for focus.meet.jitsi
prosody_1 | mod_component info Disconnecting component, <stream:error> is: <stream:error><not-authorized xmlns='urn:ietf:params:xml:ns:xmpp-streams'/><text xmlns='urn:ietf:params:xml:ns:xmpp-streams'>Given token does not match calculated token</text></stream:error>
prosody_1 | jcp55fcc7b9b730 info component disconnected: focus.meet.jitsi (stream error)
jicofo_1 | Jicofo 2020-04-19 18:04:58.812 SEVERE: [33] org.jitsi.meet.ComponentMain.log() not-authorized, host:xmpp.meet.jitsi, port:5347
jicofo_1 | org.xmpp.component.ComponentException: not-authorized
jicofo_1 | at org.jivesoftware.whack.ExternalComponent.connect(ExternalComponent.java:243)
jicofo_1 | at org.jivesoftware.whack.ExternalComponentManager.addComponent(ExternalComponentManager.java:242)
jicofo_1 | at org.jivesoftware.whack.ExternalComponentManager.addComponent(ExternalComponentManager.java:222)
jicofo_1 | at org.jitsi.meet.ComponentMain.lambda$getConnectCallable$0(ComponentMain.java:285)
jicofo_1 | at org.jitsi.retry.RetryStrategy$TaskRunner.run(RetryStrategy.java:193)
jicofo_1 | at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
jicofo_1 | at java.util.concurrent.FutureTask.run(FutureTask.java:266)
jicofo_1 | at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
jicofo_1 | at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
jicofo_1 | at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
jicofo_1 | at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
jicofo_1 | at java.lang.Thread.run(Thread.java:748) |
+1 |
Have you updated the images with docker-compose pull? |
Yes, I did do a docker-compose pull. Also fresh git clone today. |
Facing same issue after normal docker-compose up:
|
Someone has discovered what is wrong and very helpfully explained it here: https://community.jitsi.org/t/help-regarding-failing-docker-based-setup/33658/5 |
Deleting ~/.jitsi-meet-cfg solved my issue. |
I don't know if this is normal or if I have to open up any ports on my firewall or what.
I changed what seemed to be the defaults for a few things in .env
nothing else.
The text was updated successfully, but these errors were encountered: