miak3d
IImmich
•Created by miak3d on 8/12/2023 in #help-desk-support
502 through reverse proxy after updating to 1.72.2
@Alex I figured it out, might be worth adding it to your unraid docs. On unRAID if you run NPM on br0 which i think most of us do, and immich through docker compose runs on immich_default, you cannot communicate between the 2 custom networks. You need to connect NPM to both the br0 and the immich_default network which has to be done through the console with a docker network connect immich_default containername then you can use immich_proxy:8080 in NPM
13 replies
IImmich
•Created by miak3d on 8/12/2023 in #help-desk-support
502 through reverse proxy after updating to 1.72.2
@Alex wouldnt the proxy work via IP:port then? Did something change with 1.72.0 that affects proxy's? I've been using it in this configuration for 8 months or so
13 replies
IImmich
•Created by miak3d on 8/12/2023 in #help-desk-support
502 through reverse proxy after updating to 1.72.2
@Alex separate container, was working prior to 1.72.0 in this configuration. tried changing it to the ip:port as well but still gt the 502
13 replies
IImmich
•Created by miak3d on 8/12/2023 in #help-desk-support
502 through reverse proxy after updating to 1.72.2
@Alex tried that, same issue.
13 replies
IImmich
•Created by miak3d on 8/12/2023 in #help-desk-support
502 through reverse proxy after updating to 1.72.2
13 replies
IImmich
•Created by miak3d on 8/12/2023 in #help-desk-support
502 through reverse proxy after updating to 1.72.2
compose: https://pastebin.com/ReA3Q81e
13 replies
IImmich
•Created by miak3d on 4/13/2023 in #help-desk-support
502 through nginx proxy manager after reboot
i assume there probably isnt an easy way to backup/restore the db is there
52 replies
IImmich
•Created by miak3d on 4/13/2023 in #help-desk-support
502 through nginx proxy manager after reboot
unrelated question, i know you guys dont support the unraid community version that is not using docker compose, but if i were to switch to that i would likely have to redo everythign correct?
52 replies
IImmich
•Created by miak3d on 4/13/2023 in #help-desk-support
502 through nginx proxy manager after reboot
unraid doesnt use docker compose normally unfortunately
52 replies
IImmich
•Created by miak3d on 4/13/2023 in #help-desk-support
502 through nginx proxy manager after reboot
if i take it off of the immich_default network i assume that it wont resolve then, correct?
52 replies
IImmich
•Created by miak3d on 4/13/2023 in #help-desk-support
502 through nginx proxy manager after reboot
now the real question is, there is no way to force a container in unraid to connect to two networks, its apaprently a manual cli process each time the container restarts
52 replies
IImmich
•Created by miak3d on 4/13/2023 in #help-desk-support
502 through nginx proxy manager after reboot
interesting, that works
52 replies
IImmich
•Created by miak3d on 4/13/2023 in #help-desk-support
502 through nginx proxy manager after reboot
sorry, im not sure i understand how to test it inside the docker network :/
52 replies
IImmich
•Created by miak3d on 4/13/2023 in #help-desk-support
502 through nginx proxy manager after reboot
no, npm is using the ip:port of the immich_proxy - ip:2283 - http://immich_proxy:8080 does not resolve on my network
52 replies
IImmich
•Created by miak3d on 4/13/2023 in #help-desk-support
502 through nginx proxy manager after reboot
i attached NPM to the same network, still getting the 502
52 replies
IImmich
•Created by miak3d on 4/13/2023 in #help-desk-support
502 through nginx proxy manager after reboot
[error] 6208#6208: *174125 connect() failed (113: No route to host) while connecting to upstream, client: 69.167.12.35, server: immich.miakbox.com, request: "HEAD /home HTTP/1.1", upstream: "http://192.168.0.50:2283/home", host: "immich.miakbox.com"
52 replies
IImmich
•Created by miak3d on 4/13/2023 in #help-desk-support
502 through nginx proxy manager after reboot
then after updating i see tons of these:
52 replies
IImmich
•Created by miak3d on 4/13/2023 in #help-desk-support
502 through nginx proxy manager after reboot
882#882: *138658 an upstream response is buffered to a temporary file /var/cache/nginx/proxy_temp/1/79/0000012791 while reading upstream, client: 192.168.0.110, server: immich.miakbox.com, request: "GET /api/asset HTTP/1.1", upstream: "http://192.168.0.50:2283/api/asset", host: "immich.miakbox.com"
52 replies
IImmich
•Created by miak3d on 4/13/2023 in #help-desk-support
502 through nginx proxy manager after reboot
looking through the logs on NPM i think you guys are on the right path with the network stuff, granted, im not sure what im reading here but i see this before i updated:
52 replies
IImmich
•Created by miak3d on 4/13/2023 in #help-desk-support
502 through nginx proxy manager after reboot
you guys might not know the answer to this but is there a way to change immich to run on a different docker network vs me moving my proxy to a different network to see if that fixes things?
52 replies