-
DescriptionOS : Debian 11 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 refusedWhen 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-proxI have tried a docker stop/start to no avail Version0.7.9 Steps to Reproduce
ScreenshotsStuck on the step 1 of this screen : Logs2024/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" "-"Platformdesktop DevicePC Operating SystemDebian 11 BrowserChrome Additional ContextNo response Code of Conduct
|
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 13 replies
-
|
Hi, It seem that the frontend / backend don't share the same network. Can you please try with the one provided ?
ps: I closed the issue and change it as a discussion |
Beta Was this translation helpful? Give feedback.
-
|
Yes sure ! So I did : docker stop teemii-frontend teemii-backend
docker rm teemii-frontend teemii-backendand then a : docker-compose --version
Docker Compose version v2.23.3
docker-compose up -dBut it throws this error : service "teemii-backend" refers to undefined volume teemii-data: invalid compose projectI checked and I do have a volume named teemii-data : it must have been created during this step.
I'm not sure if I did something wrong at this point, but I'm using the docker-compose file that is included in this repo. :( |
Beta Was this translation helpful? Give feedback.
-
|
Are you sure that you are using the docker-compose file from the develop branch? |
Beta Was this translation helpful? Give feedback.
-
|
I was not using the develop branch but the "main" one. Using the develop branch allowed to "up -d" : I can see that both containers are up : But i'm still stuck on this screen :
While watching the logs I have the same errors as before : Not sure if I should be seeing anything while netstating but the port 3000 looks not listening : Of course, nothing else is currently listening on port 3000 |
Beta Was this translation helpful? Give feedback.
-
|
(or port 1555, I just checked) |
Beta Was this translation helpful? Give feedback.
-
|
teemii-teemii-backend-1 is the name of your Docker Container? If yes you need to recreate then as:
|
Beta Was this translation helpful? Give feedback.
-
|
I tried stopping and then renaming the container : no change As you can see, everything is clean. Then : Then the compose up -d : As you can see, the containers are automatically created under this name o_o The problem is still the same. Logs from the frontend are the same I shared before. I truly don't know what could go wrong :( |
Beta Was this translation helpful? Give feedback.
-
|
It's hard to say what's wrong.
Then, it seems that the backend doesn't really start. This should help us to see things more clearly |
Beta Was this translation helpful? Give feedback.
-
|
No, here are the info from the processor : Intel(R) Atom(TM) CPU N2800 Am I out of luck ? |
Beta Was this translation helpful? Give feedback.
-
|
I've just had a look and, in truth, it shouldn't be. Still in the same directory:
|
Beta Was this translation helpful? Give feedback.
-
|
No more luck trying this :( i also tried to "rebuild" : But I can't npm start either, i'm maybe doomed :/ |
Beta Was this translation helpful? Give feedback.
-
|
So I've worked out what's wrong, but it's not good news. |
Beta Was this translation helpful? Give feedback.
-
|
Very good job on finding out what's wrong, couldn't have been easy 😱 I will still keep an eye on your project for when I'll upgrade my server! I can't wait !! Thank you for your time <3 |
Beta Was this translation helpful? Give feedback.
-
|
Does it mean the teemii docker will not work on arm64? |
Beta Was this translation helpful? Give feedback.
So I've worked out what's wrong, but it's not good news.
Teemii uses some modules that require a processor with SSE4 instruction sets.
Yours has : Intel® SSE2, Intel® SSE3, Intel® SSSE3...
Sorry 😔