Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps - Status | Demo | Docs | Install
  1. Cloudron Forum
  2. Immich
  3. Immich stopped working since last Cloudron upgrade

Immich stopped working since last Cloudron upgrade

Scheduled Pinned Locked Moved Immich
3 Posts 3 Posters 27 Views 3 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • SansGuidonS Offline
    SansGuidonS Offline
    SansGuidon
    wrote last edited by SansGuidon
    #1
    18 06:34:19 7670:C 18 Jan 2026 05:34:19.029 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
    Jan 18 06:37:25 2026-01-18 05:37:25,586 INFO reaped unknown pid 85694 (terminated by SIGTERM)
    Jan 18 06:37:25 2026-01-18 05:37:25,586 WARN exited: server (exit status 1; not expected)
    Jan 18 06:37:25 Killing api process
    Jan 18 06:37:25 at ErrorResponse (/usr/src/app/server/node_modules/.pnpm/postgres@3.4.7/node_modules/postgres/cjs/src/connection.js:794:26)
    Jan 18 06:37:25 at Readable.push (node:internal/streams/readable:392:5)
    Jan 18 06:37:25 at Socket.data (/usr/src/app/server/node_modules/.pnpm/postgres@3.4.7/node_modules/postgres/cjs/src/connection.js:315:9)
    Jan 18 06:37:25 at Socket.emit (node:events:519:28)
    Jan 18 06:37:25 at TCP.onStreamRead (node:internal/stream_base_commons:189:23)
    Jan 18 06:37:25 at TCP.onStreamRead (node:internal/stream_base_commons:189:23) {
    Jan 18 06:37:25 at addChunk (node:internal/streams/readable:561:12)
    Jan 18 06:37:25 at handle (/usr/src/app/server/node_modules/.pnpm/postgres@3.4.7/node_modules/postgres/cjs/src/connection.js:480:6)
    Jan 18 06:37:25 at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)
    Jan 18 06:37:25 code: '42501',
    Jan 18 06:37:25 file: 'aclchk.c',
    Jan 18 06:37:25 line: '2950',
    Jan 18 06:37:25 microservices worker error: PostgresError: must be owner of extension vchord, stack: PostgresError: must be owner of extension vchord
    Jan 18 06:37:25 microservices worker exited with code 1
    Jan 18 06:37:25 routine: 'aclcheck_error'
    Jan 18 06:37:25 severity: 'ERROR',
    Jan 18 06:37:25 severity_local: 'ERROR',
    Jan 18 06:37:25 }
    Jan 18 06:37:26 2026-01-18 05:37:26,589 INFO spawned: 'server' with pid 85706
    Jan 18 06:37:27 2026-01-18 05:37:27,590 INFO success: server entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
    Jan 18 06:37:28 (Use `node --trace-warnings ...` to show where the warning was created)
    Jan 18 06:37:28 (node:85706) ExperimentalWarning: WASI is an experimental feature and might change at any time
    Jan 18 06:37:28 Missing history for endpoint: Retrieve auth status
    Jan 18 06:37:28 Starting api worker
    Jan 18 06:37:28 Starting microservices worker
    Jan 18 06:37:30 => Healthcheck error: Error: connect ECONNREFUSED 172.18.20.11:2283
    Jan 18 06:37:30 Missing history for endpoint: Retrieve auth status
    Jan 18 06:37:30 Missing history for endpoint: Retrieve auth status
    Jan 18 06:37:31 2026-01-18T05:37:31Z
    Jan 18 06:37:31 [Nest] 85706 - 01/18/2026, 5:37:31 AM LOG [Microservices:DatabaseService] Updating VectorChord extension to 0.5.3
    Jan 18 06:37:31 [Nest] 85706 - 01/18/2026, 5:37:31 AM LOG [Microservices:WebsocketRepository] Initialized websocket server
    Jan 18 06:37:31 [Nest] 85706 - 01/18/2026, 5:37:31 AM WARN [Microservices:DatabaseService] The VectorChord extension can be updated to 0.5.3.
    Jan 18 06:37:31 (Use `node --trace-warnings ...` to show where the warning was created)
    Jan 18 06:37:31 (Use `node --trace-warnings ...` to show where the warning was created)
    Jan 18 06:37:31 (node:85706) ExperimentalWarning: WASI is an experimental feature and might change at any time
    Jan 18 06:37:31 (node:85717) ExperimentalWarning: WASI is an experimental feature and might change at any time
    Jan 18 06:37:31 2026-01-18 05:37:31,405 INFO reaped unknown pid 85717 (terminated by SIGTERM)
    Jan 18 06:37:31 2026-01-18 05:37:31,405 WARN exited: server (exit status 1; not expected)
    Jan 18 06:37:31 Immich attempted to update the extension, but failed to do so.
    Jan 18 06:37:31 Killing api process
    Jan 18 06:37:31 Please run 'ALTER EXTENSION vchord UPDATE' manually as a superuser.
    Jan 18 06:37:31 PostgresError: must be owner of extension vchord
    Jan 18 06:37:31 Query failed : {
    Jan 18 06:37:31 See https://docs.immich.app/guides/database-queries for how to query the database.
    Jan 18 06:37:31 This may be because Immich does not have the necessary permissions to update the extension.
    Jan 18 06:37:31 at ErrorResponse (/usr/src/app/server/node_modules/.pnpm/postgres@3.4.7/node_modules/postgres/cjs/src/connection.js:794:26)
    Jan 18 06:37:31 at ErrorResponse (/usr/src/app/server/node_modules/.pnpm/postgres@3.4.7/node_modules/postgres/cjs/src/connection.js:794:26)
    Jan 18 06:37:31 at ErrorResponse (/usr/src/app/server/node_modules/.pnpm/postgres@3.4.7/node_modules/postgres/cjs/src/connection.js:794:26)
    Jan 18 06:37:31 at Readable.push (node:internal/streams/readable:392:5)
    Jan 18 06:37:31 at Readable.push (node:internal/streams/readable:392:5)
    Jan 18 06:37:31 at Readable.push (node:internal/streams/readable:392:5)
    Jan 18 06:37:31 at Socket.data (/usr/src/app/server/node_modules/.pnpm/postgres@3.4.7/node_modules/postgres/cjs/src/connection.js:315:9)
    Jan 18 06:37:31 at Socket.data (/usr/src/app/server/node_modules/.pnpm/postgres@3.4.7/node_modules/postgres/cjs/src/connection.js:315:9)
    Jan 18 06:37:31 at Socket.data (/usr/src/app/server/node_modules/.pnpm/postgres@3.4.7/node_modules/postgres/cjs/src/connection.js:315:9)
    Jan 18 06:37:31 at Socket.emit (node:events:519:28)
    Jan 18 06:37:31 at Socket.emit (node:events:519:28)
    

    I've stopped the app as it was endlessly crashing then have attempted a restore to last backup but the restore action does nothing, the popup asking confirmation for the restore action just stays visible when I confirm the restore.

    It's confusing.

    Should I go mess up with postgres somewhere? And what happened 🙃??
    Thanks for any help!😅

    About me / Now

    1 Reply Last reply
    0
    • SansGuidonS SansGuidon marked this topic as a question
    • imc67I Offline
      imc67I Offline
      imc67
      translator
      wrote last edited by
      #2

      Same here after auto update!

      https://forum.cloudron.io/topic/14909/side-effects-cloudron-v-9.0.16-app.immich.cloudronapp@1.95.1

      1 Reply Last reply
      0
      • girishG Do not disturb
        girishG Do not disturb
        girish
        Staff
        wrote last edited by
        #3

        Please follow the other thread since it is a platform issue.

        1 Reply Last reply
        0
        • girishG girish locked this topic
        • girishG girish marked this topic as a regular topic
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        • Login

        • Don't have an account? Register

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • Bookmarks
        • Search