sashk0 Comments - Answer Overflow

sashk0

•Created by Mavor on 10/17/2023 in #help-desk-support

After upgrade to v1.82.0 immich is broken (Admin->Repair hangs the server for good)

so, one step closer to solution? 🙂 I haven't changed my docker-compose.yaml after I updated the version. that's my proxy config for proxy instance:

immich-proxy:
    container_name: immich_proxy
    image: ghcr.io/immich-app/immich-proxy:${IMMICH_VERSION:-release}
    environment:
      # Make sure these values get passed through from the env file
      - IMMICH_SERVER_URL
      - IMMICH_WEB_URL
    ports:
      - 2283:8080
    depends_on:
      - immich-server
      - immich-web
    restart: always

immich-proxy:
    container_name: immich_proxy
    image: ghcr.io/immich-app/immich-proxy:${IMMICH_VERSION:-release}
    environment:
      # Make sure these values get passed through from the env file
      - IMMICH_SERVER_URL
      - IMMICH_WEB_URL
    ports:
      - 2283:8080
    depends_on:
      - immich-server
      - immich-web
    restart: always

is it somehow wrong?

104 replies

IImmich

•Created by Mavor on 10/17/2023 in #help-desk-support

After upgrade to v1.82.0 immich is broken (Admin->Repair hangs the server for good)

I have the same issue with /repair. it just hangs up and throws 500 error. I've checked logs, looks like all is up and running. in logs of immich_server:

[Nest] 6  - 10/17/2023, 6:23:27 PM   ERROR [ExceptionsHandler] Connection terminated due to connection timeout
Error: Connection terminated due to connection timeout
    at Connection.<anonymous> (/usr/src/app/node_modules/pg/lib/client.js:132:73)
    at Object.onceWrapper (node:events:628:28)
    at Connection.emit (node:events:514:28)
    at Socket.<anonymous> (/usr/src/app/node_modules/pg/lib/connection.js:63:12)
    at Socket.emit (node:events:514:28)

[Nest] 6  - 10/17/2023, 6:23:27 PM   ERROR [ExceptionsHandler] Connection terminated due to connection timeout
Error: Connection terminated due to connection timeout
    at Connection.<anonymous> (/usr/src/app/node_modules/pg/lib/client.js:132:73)
    at Object.onceWrapper (node:events:628:28)
    at Connection.emit (node:events:514:28)
    at Socket.<anonymous> (/usr/src/app/node_modules/pg/lib/connection.js:63:12)
    at Socket.emit (node:events:514:28)

and in immich_proxy:

2023/10/17 18:30:36 [error] 44#44: *310 upstream timed out (110: Operation timed out) while reading response header from upstream, client: 192.168.0.19, server: , request: "GET /admin/repair/__data.json?x-sveltekit-invalidated=01 HTTP/1.1", upstream: "http://172.20.0.4:3000/admin/repair/__data.json?x-sveltekit-invalidated=01", host: "192.168.0.12:2283", referrer: "http://192.168.0.12:2283/admin/jobs-status"

2023/10/17 18:30:36 [error] 44#44: *310 upstream timed out (110: Operation timed out) while reading response header from upstream, client: 192.168.0.19, server: , request: "GET /admin/repair/__data.json?x-sveltekit-invalidated=01 HTTP/1.1", upstream: "http://172.20.0.4:3000/admin/repair/__data.json?x-sveltekit-invalidated=01", host: "192.168.0.12:2283", referrer: "http://192.168.0.12:2283/admin/jobs-status"

any idea what was broken?

104 replies

Gaming

Programming