librephotos: Can't Connect to Backend Server

Greetings,

I’ve LibrePhotos installed on Synology (Docker) and it was working perfectly, however, after a restart (for an update) I am no longer able to longin 😦 I am getting this error

No connection to backend server.

Few lines of from the log:

2021/03/29 15:10:28 [error] 21#21: *28 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.160.1, server: , request: "GET /api/sitesettings/ HTTP/1.1", upstream: "http://192.168.160.2:8001/api/sitesettings/", host: "192.168.2.201:3333", referrer: "http://192.168.2.201:3333/login",

2021/03/29 15:12:09 [error] 21#21: *46 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.160.1, server: , request: "GET /api/sitesettings/ HTTP/1.1", upstream: "http://192.168.160.2:8001/api/sitesettings/", host: "192.168.2.201:3333", referrer: "http://192.168.2.201:3333/login",

2021/03/29 15:14:56 [error] 21#21: *56 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.160.1, server: , request: "POST /api/auth/token/obtain/ HTTP/1.1", upstream: "http://192.168.160.2:8001/api/auth/token/obtain/", host: "192.168.2.201:3333", referrer: "http://192.168.2.201:3333/login",

192.168.160.1 - - [29/Mar/2021:15:14:56 +0000] "POST /api/auth/token/obtain/ HTTP/1.1" 502 559 "http://192.168.2.201:3333/login" "Mozilla/5.0 (Macintosh; Intel Mac OS X 11_2_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.192 Safari/537.36"

Although all containers are working just fine and healthy. How can I fix this? any ideas?

About this issue

Original URL
State: closed
Created 3 years ago
Comments: 20 (3 by maintainers)

Commits related to this issue

Merge pull request #221 from LibrePhotos/renovate/dnd-kit-monorepo Update dnd-kit monorepo — committed to AnkurPrabhu/librephotos by derneuere a year ago

Most upvoted comments

Hi @bhusain966. I was looking into the docker-compose.yml file. Though docker-compose defines it’s own default network, you can try declaring all of the containers under the same network. You can also make use of your default network throughout the containers. Could you use this reference to do the same? This solved similar issues that I faced previously 😄

ThirumlaDevi on Mar 29, 2021