dokkaner / teemii

A versatile, self-hosted manga reader and manager with extensible agent-based metadata retrieval
https://www.teemii.io
MIT License
308 stars 19 forks source link

[Install] Docker CLI - Can't connect to database #38

Closed imRadwolf closed 9 months ago

imRadwolf commented 9 months ago

Description

OS : Debian 11 Docker : Docker version 24.0.7

I followed the docker cli documentation to the letter but I still have this error in the frontend container :

docker logs teemii-frontend

2024/01/04 21:38:10 [error] 33#33: *3 connect() failed (111: Connection refused) while connecting to upstream, client: xx.xx.xx.xx, server: , request: "POST /api/v1/setup/deployDB HTTP/1.1", upstream: "http://172.20.0.3:3000/api/v1/setup/deployDB", host: "xxxxxx.fr:8080", referrer: "http://xxxxxx.re:8080/wizard"

I have anonymized my IP and domain, but there's a problem with the "upstream" private IP, it looks like the port isn't listening :

ping 172.20.0.3
PING 172.20.0.3 (172.20.0.3) 56(84) bytes of data.
64 bytes from 172.20.0.3: icmp_seq=1 ttl=64 time=0.702 ms
64 bytes from 172.20.0.3: icmp_seq=2 ttl=64 time=0.130 ms
64 bytes from 172.20.0.3: icmp_seq=3 ttl=64 time=0.128 ms
^C
--- 172.20.0.3 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2009ms
rtt min/avg/max/mdev = 0.128/0.320/0.702/0.270 ms

telnet 172.20.0.3 3000
Trying 172.20.0.3...
telnet: Unable to connect to remote host: Connection refused

When I use netstat on my server, the 8080 port of the frontend is listening, but the backend one isn't :

netstat -nlapute | grep -i listen | grep docker
tcp        0      0 0.0.0.0:8080            0.0.0.0:*               LISTEN      0          92592899   3392864/docker-prox 
tcp6       0      0 :::8080                 :::*                    LISTEN      0          92590796   3392873/docker-prox

I have tried a docker stop/start to no avail

Version

0.7.9

Steps to Reproduce

  1. follow the docker cli until the end of step 4
  2. the port 3000 isn't listening

Screenshots

Stuck on the step 1 of this screen : image

Logs

2024/01/04 21:38:10 [error] 33#33: *3 connect() failed (111: Connection refused) while connecting to upstream, client: xx.xx.xx.xx, server: , request: "POST /api/v1/setup/deployDB HTTP/1.1", upstream: "http://172.20.0.3:3000/api/v1/setup/deployDB", host: "xxxxxx.re:8080", referrer: "http://xxxxxx.re:8080/wizard"
xx.xx.xx.xx - - [04/Jan/2024:21:38:10 +0000] "POST /api/v1/setup/deployDB HTTP/1.1" 502 559 "http://xxxxxx.re:8080/wizard" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36" "-"
xx.xx.xx.xx - - [04/Jan/2024:21:38:10 +0000] "POST /api/v1/setup/deployDB HTTP/1.1" 502 559 "http://xxxxxx.re:8080/wizard" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36" "-"
2024/01/04 21:38:10 [error] 33#33: *3 connect() failed (111: Connection refused) while connecting to upstream, client: xx.xx.xx.xx, server: , request: "POST /api/v1/setup/deployDB HTTP/1.1", upstream: "http://172.20.0.3:3000/api/v1/setup/deployDB", host: "xxxxxx.re:8080", referrer: "http://xxxxxx.re:8080/wizard"
2024/01/04 21:38:10 [error] 33#33: *3 connect() failed (111: Connection refused) while connecting to upstream, client: xx.xx.xx.xx, server: , request: "POST /api/v1/setup/deployDB HTTP/1.1", upstream: "http://172.20.0.3:3000/api/v1/setup/deployDB", host: "xxxxxx.re:8080", referrer: "http://xxxxxx.re:8080/wizard"
xx.xx.xx.xx - - [04/Jan/2024:21:38:10 +0000] "POST /api/v1/setup/deployDB HTTP/1.1" 502 559 "http://xxxxxx.re:8080/wizard" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36" "-"

Platform

desktop

Device

PC

Operating System

Debian 11

Browser

Chrome

Additional Context

No response

Code of Conduct