Docker-jitsi-meet: "/usr/share/jitsi-meet/"https:/DOMAIN"/http-bind" failed (2: No such file or directory),
Hi,
I have been using Jitsi with docker for a year or so with no proiblems. I have a workign Apache reverse proxy as well since I let Apache to handle the SSL certs.
This morning, I recreated this container, generated the passwords, edited the .env files, removed all the files in the config folder. The I ran the container like I did in the past with docker-compose up
It seems like everything works until I am about to enter a room, then I get
You have been disconnected. You may want to check your network connection
with the relevant errors below
I am on Debian Testing, using Apache 2.4.43
It works! Now point your BOSH client to this URL to connect to Prosody.
For more information see Prosody: Setting up BOSH.
jicofo_1 | Jicofo 2020-04-08 14:59:11.612 INFO: [1] org.jitsi.xmpp.component.ComponentBase.log() ping timeout: 5000 ms
jicofo_1 | Jicofo 2020-04-08 14:59:11.612 INFO: [1] org.jitsi.xmpp.component.ComponentBase.log() ping threshold: 3
prosody_1 | jcp55b93e217920 info Incoming Jabber component connection
prosody_1 | focus.meet.jitsi:component info External component successfully authenticated
jvb_1 | SCTP JNI load: Linux OS detected
jvb_1 | SCTP lib loaded
jvb_1 | =====>: org_jitsi_modified_sctp4j_SctpJni.c calling init
jvb_1 | =====>: org_jitsi_modified_sctp4j_SctpJni.c about to set SCTP_DEBUG_ALL
jvb_1 | Apr 08, 2020 2:59:11 PM org.jitsi.utils.logging2.LoggerImpl log
jvb_1 | INFO: Performed a successful health check in 1680ms. Sticky failure: false
jicofo_1 | Jicofo 2020-04-08 14:59:15.218 INFO: [30] org.jitsi.jicofo.xmpp.BaseBrewery.processInstanceStatusChanged().329 Added brewery instance: [email protected]/cec15074576f
jicofo_1 | Jicofo 2020-04-08 14:59:15.218 WARNING: [30] org.jitsi.jicofo.bridge.BridgeSelector.log() No pub-sub node mapped for [email protected]/cec15074576f
jicofo_1 | Jicofo 2020-04-08 14:59:15.220 INFO: [30] org.jitsi.jicofo.bridge.Bridge.log() Setting max total packet rate of 50800.0
jicofo_1 | Jicofo 2020-04-08 14:59:15.220 INFO: [30] org.jitsi.jicofo.bridge.Bridge.log() Setting average participant packet rate of 500
jicofo_1 | Jicofo 2020-04-08 14:59:15.239 INFO: [30] org.jitsi.jicofo.bridge.BridgeSelector.log() Added new videobridge: Bridge[[email protected]/cec15074576f, relayId=null, region=null, s
tress=0.00]
jicofo_1 | Jicofo 2020-04-08 14:59:15.242 INFO: [45] org.jitsi.jicofo.bridge.JvbDoctor.log() Scheduled health-check task for: [email protected]/cec15074576f
jvb_1 | Apr 08, 2020 2:59:21 PM org.jitsi.utils.logging2.LoggerImpl log
jvb_1 | INFO: create_conf, id=ef72be3b0d15ac5d gid=null logging=false
jvb_1 | Apr 08, 2020 2:59:21 PM org.jitsi.utils.logging2.LoggerImpl log
jvb_1 | INFO: Performed a successful health check in 12ms. Sticky failure: false
web_1 | 172.23.0.1 - - [08/Apr/2020:14:59:30 -0500] "GET /SmoothBossesScrewSufficiently HTTP/1.1" 200 13653 "https://DOMAIN/SmoothBossesScrewSufficiently" "Mozilla/5.0 (X11; Linux x86_64) AppleWe
bKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.162 Safari/537.36"
web_1 | 2020/04/08 14:59:31 [error] 240#240: *1 open() "/usr/share/jitsi-meet/"https:/DOMAIN"/http-bind" failed (2: No such file or directory), client: 172.23.0.1, server: _, request: "POST /%22h
ttps:/DOMAIN%22/http-bind?room=smoothbossesscrewsufficiently HTTP/1.1", host: "DOMAIN", referrer: "https://DOMAIN/SmoothBossesScrewSufficiently"
web_1 | 172.23.0.1 - - [08/Apr/2020:14:59:31 -0500] "POST /%22https:/DOMAIN%22/http-bind?room=smoothbossesscrewsufficiently HTTP/1.1" 404 403 "https://DOMAIN/SmoothBossesScrewSufficien
tly" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.162 Safari/537.36"
jvb_1 | Apr 08, 2020 2:59:31 PM org.jitsi.utils.logging2.LoggerImpl log
jvb_1 | INFO: create_conf, id=f5cc8666c850a5dd gid=null logging=false
jvb_1 | Apr 08, 2020 2:59:31 PM org.jitsi.utils.logging2.LoggerImpl log
jvb_1 | INFO: Performed a successful health check in 14ms. Sticky failure: false
web_1 | 172.23.0.1 - - [08/Apr/2020:14:59:38 -0500] "GET / HTTP/1.1" 200 13653 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.162 Safari/537.36"
jicofo_1 | Jicofo 2020-04-08 14:59:41.081 INFO: [33] org.jitsi.jicofo.ComponentsDiscovery.log() New component discovered: focus.meet.jitsi, null
jvb_1 | Apr 08, 2020 2:59:41 PM org.jitsi.utils.logging2.LoggerImpl log
jvb_1 | INFO: create_conf, id=3b6b00c3f724deb7 gid=null logging=false
jvb_1 | Apr 08, 2020 2:59:41 PM org.jitsi.utils.logging2.LoggerImpl log
jvb_1 | INFO: Performed a successful health check in 16ms. Sticky failure: false
web_1 | 172.23.0.1 - - [08/Apr/2020:14:59:45 -0500] "GET /ProblematicSpinsArriveEast HTTP/1.1" 200 13653 "https://DOMAIN/" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko)
Chrome/80.0.3987.162 Safari/537.36"
web_1 | 2020/04/08 14:59:47 [error] 240#240: *1 open() "/usr/share/jitsi-meet/"https:/DOMAIN"/http-bind" failed (2: No such file or directory), client: 172.23.0.1, server: _, request: "POST /%22h
ttps:/DOMAIN%22/http-bind?room=problematicspinsarriveeast HTTP/1.1", host: "DOMAIN", referrer: "https://DOMAIN/ProblematicSpinsArriveEast"
web_1 | 172.23.0.1 - - [08/Apr/2020:14:59:47 -0500] "POST /%22https:/DOMAIN%22/http-bind?room=problematicspinsarriveeast HTTP/1.1" 404 403 "https://DOMAIN/ProblematicSpinsArriveEast" "
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.162 Safari/537.36"
jvb_1 | Apr 08, 2020 2:59:51 PM org.jitsi.utils.logging2.LoggerImpl log
jvb_1 | INFO: create_conf, id=c56dbd68fe2eae37 gid=null logging=false
jvb_1 | Apr 08, 2020 2:59:51 PM org.jitsi.utils.logging2.LoggerImpl log
Here is my apache proxy, I am pretty sure this is correct since it work the whole time
ProxyPreserveHost on
RequestHeader set X-Forwarded-Proto "https"
ProxyPass / http://127.0.0.1:28000/
ProxyPassReverse / http://127.0.0.1:28000/
ProxyPreserveHost on
ProxyPass /http-bind http://localhost:28000/http-bind/
ProxyPassReverse /http-bind http://localhost:28000/http-bind/
gerroon
All 6 comments
I am getting the same error about the http-bind url being appended to that /usr/share path but my install is working otherwise. Maybe don't fixate on that error message.
I had massive issues trying to get the docker jitsi-meet to work on a SUBdomain (e.g. meet.mydomain.com). It works on the main domain (mydomain.com) but when I try to install on a subdomain I am getting funny issues including those "you have been disconnected" and "theres been some issue, trying to reconnect" error messages you posted.
It used to work with the previous docker image when I installed on the main domain and then used the subdomain. Now it won't work on a subdomain at all. Maybe thats your issue as well?
normen
on 9 Apr 2020
@normen
Yes that sounds like the issue. Please see the antonanders comment here, https://github.com/jitsi/docker-jitsi-meet/issues/404
That takes care of the bind issue but I am still having other issues.
gerroon
on 9 Apr 2020
Did you by any chance uncomment the ipv6 option as well?
normen
on 9 Apr 2020
I've had the same problems.
My solution: Don't use quotes for PUBLIC_URL in .env:
PUBLIC_URL=https://video.akdigitalegesellschaft.de
sventhomsen
on 9 Apr 2020
Hm at least I don't.. I use pretty much the vanilla docker setup, for updating I use a shell script that backs up my users, clears out everything and just sed -i replaces the relevant stuff in .env and config.js / interface_config.js. Then the plain http goes out through nginx on the docker host.
That said, everything seems to be working for me, I am just getting a whole bunch of Address discovery through STUN failed errors in the jvb log.
normen
on 9 Apr 2020
quot
Thanks for your solution. Removing the quotation marks from the value of PUBLIC_URL solved my problem, too, although it worked in the last docker-jitsi version...
Example:
CORRECT:
PUBLIC_URL=https://meet.jit.si
WRONG:
PUBLIC_URL="https://meet.jit.si"
chrishoerl
on 12 Apr 2020
Related issues
mrWodoo
路
5Comments
Cyborgscode
路
5Comments
tsproesser
路
8Comments
kheir95
路
6Comments
mfts
路
6Comments
Most helpful comment
I've had the same problems.
My solution: Don't use quotes for PUBLIC_URL in .env:
PUBLIC_URL=https://video.akdigitalegesellschaft.de