502 through reverse proxy after updating to 1.72.2
I updated from pre 1.72.0 today and now im getting a 502 through my reverse proxy whereas i was not prior to updating. I am on unraid using the docker compose method. I can successfully access immich through the ip:port but once i go through the proxy i get a 502
11 Replies
compose: https://pastebin.com/ReA3Q81e
Pastebin
version: "3.8"services: immich-server: container_name: immich_s...
Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
Pastebin
###################################################################...
Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
restart your proxy perhaps?
@Alex tried that, same issue.
I don't see npm on the same docker-compose file with Immich though
@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
I think your NPM container and Immich's network cannot see each other
if you attach to the shell of your NPM container, I assume you cannot
curl immich-server at all@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
No we didn’t change anything regarding that mechanism. Have you try completely bring down and bring up the entire stack as well as the npm container?
@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
Thank you for reporting back