Quantcast
Channel: Debian User Forums
Viewing all articles
Browse latest Browse all 3395

Jitsi docker-compose: Unable to connect

$
0
0
Yesterday, I updated my Debian stable server. It's a v-server, and it only runs a Jitsi video server. I use this image: https://github.com/jitsi/docker-jitsi-meet
Have used it for years. After I updated Debian, Jitsi does not work properly anymore. When I try to connect to it from a browser, I get an "unable to connect" error.

On the server, I get:

Code:

# docker psCONTAINER ID   IMAGE                         COMMAND   CREATED          STATUS          PORTS                                                                      NAMES1f8f03f107bf   jitsi/web:stable-9584-1       "/init"   25 minutes ago   Up 44 seconds   0.0.0.0:80->80/tcp, :::80->80/tcp, 0.0.0.0:443->443/tcp, :::443->443/tcp   docker-jitsi-meet-stable_web_1cd4fced3a109   jitsi/jvb:stable-9584-1       "/init"   25 minutes ago   Up 44 seconds   127.0.0.1:8080->8080/tcp, 0.0.0.0:10000->10000/udp, :::10000->10000/udp    docker-jitsi-meet-stable_jvb_1a67557eeec43   jitsi/jicofo:stable-9584-1    "/init"   25 minutes ago   Up 45 seconds   127.0.0.1:8888->8888/tcp                                                   docker-jitsi-meet-stable_jicofo_1cccb4523ca73   jitsi/prosody:stable-9584-1   "/init"   25 minutes ago   Up 45 seconds   5222/tcp, 5269/tcp, 5280/tcp, 5347/tcp                                     docker-jitsi-meet-stable_prosody_1
So the containers seem to be running fine.

Code:

# netstat -tulpe | grep dockertcp        0      0 0.0.0.0:http            0.0.0.0:*               LISTEN      root       33576      13162/docker-proxy  tcp        0      0 localhost:8888          0.0.0.0:*               LISTEN      root       17015      1124/docker-proxy   tcp        0      0 0.0.0.0:https           0.0.0.0:*               LISTEN      root       33535      13142/docker-proxy  tcp        0      0 localhost:http-alt      0.0.0.0:*               LISTEN      root       17372      1260/docker-proxy   tcp6       0      0 [::]:http               [::]:*                  LISTEN      root       33581      13167/docker-proxy  tcp6       0      0 [::]:https              [::]:*                  LISTEN      root       33540      13147/docker-proxy  udp        0      0 0.0.0.0:10000           0.0.0.0:*                           root       17147      1197/docker-proxy   udp6       0      0 [::]:10000              [::]:*                              root       17192      1202/docker-proxy 
Looks like Jitsi is listening on ports 80 and 443, as they should.

Code:

# iptables -LChain INPUT (policy ACCEPT)target     prot opt source               destination         Chain FORWARD (policy DROP)target     prot opt source               destination         DOCKER-USER  all  --  anywhere             anywhere            DOCKER-ISOLATION-STAGE-1  all  --  anywhere             anywhere            ACCEPT     all  --  anywhere             anywhere             ctstate RELATED,ESTABLISHEDDOCKER     all  --  anywhere             anywhere            ACCEPT     all  --  anywhere             anywhere            ACCEPT     all  --  anywhere             anywhere            ACCEPT     all  --  anywhere             anywhere             ctstate RELATED,ESTABLISHEDDOCKER     all  --  anywhere             anywhere            ACCEPT     all  --  anywhere             anywhere            ACCEPT     all  --  anywhere             anywhere            ACCEPT     all  --  anywhere             anywhere             ctstate RELATED,ESTABLISHEDDOCKER     all  --  anywhere             anywhere            ACCEPT     all  --  anywhere             anywhere            ACCEPT     all  --  anywhere             anywhere            ACCEPT     all  --  anywhere             anywhere             ctstate RELATED,ESTABLISHEDDOCKER     all  --  anywhere             anywhere            ACCEPT     all  --  anywhere             anywhere            ACCEPT     all  --  anywhere             anywhere            Chain OUTPUT (policy ACCEPT)target     prot opt source               destination         Chain DOCKER (4 references)target     prot opt source               destination         ACCEPT     tcp  --  anywhere             172.20.0.2           tcp dpt:8888ACCEPT     tcp  --  anywhere             172.20.0.4           tcp dpt:httpsACCEPT     udp  --  anywhere             172.20.0.5           udp dpt:10000ACCEPT     tcp  --  anywhere             172.20.0.4           tcp dpt:httpACCEPT     tcp  --  anywhere             172.20.0.5           tcp dpt:http-altChain DOCKER-ISOLATION-STAGE-1 (1 references)target     prot opt source               destination         DOCKER-ISOLATION-STAGE-2  all  --  anywhere             anywhere            DOCKER-ISOLATION-STAGE-2  all  --  anywhere             anywhere            DOCKER-ISOLATION-STAGE-2  all  --  anywhere             anywhere            DOCKER-ISOLATION-STAGE-2  all  --  anywhere             anywhere            RETURN     all  --  anywhere             anywhere            Chain DOCKER-ISOLATION-STAGE-2 (4 references)target     prot opt source               destination         DROP       all  --  anywhere             anywhere            DROP       all  --  anywhere             anywhere            DROP       all  --  anywhere             anywhere            DROP       all  --  anywhere             anywhere            RETURN     all  --  anywhere             anywhere            Chain DOCKER-USER (1 references)target     prot opt source               destination         RETURN     all  --  anywhere             anywhere     
IP tables look fine to me as well, incoming requests are accepted.

When checking from outside, all ports seem to be closed:

Code:

$ nmap 12.34.56.78Starting Nmap 7.93 ( https://nmap.org ) at 2024-07-08 18:49 CESTNmap scan report for [domain] (12.34.56.78)Host is up (0.11s latency).All 1000 scanned ports on [domain] (12.34.56.78) are in ignored states.Not shown: 1000 closed tcp ports (conn-refused)Nmap done: 1 IP address (1 host up) scanned in 10.22 seconds
No idea why this is not working. Can anybody help here?

Statistics: Posted by sawyer22 — 2024-07-08 17:16 — Replies 0 — Views 28



Viewing all articles
Browse latest Browse all 3395

Trending Articles