#TrueNAS SCALE Immich upgrade blocked: missing PG15 → PG18 Postgres image selector

1 messages · Page 1 of 1 (latest)

balmy timber
#

Hi, I need help with upgrading Immich on TrueNAS SCALE.

Setup:

  • TrueNAS SCALE: 24.10.2.2
  • App name: immich
  • Immich App Version: v1.141.1
  • TrueNAS catalog/chart version: 1.9.24
  • Installed via TrueNAS Apps, not Docker Compose

I already migrated away from the old/deprecated storage configuration. That previous migration error is gone.

Now the upgrade fails because the app apparently still has PostgreSQL 15 selected, but the newer version requires PostgreSQL 18. The error is:

ValidationErrors: [EINVAL] values.immich.postgres_image_selector: Invalid choice: vectorchord_15_image

Normally there should be a setting in the TrueNAS app edit screen to switch the Postgres image from PG15 to PG18, but in my existing Immich app this field is not visible anywhere. I searched the app settings for Postgres / database / image selector, but I cannot find the selector.

I found a similar Reddit thread where the “Postgres Image” selection field is also missing in an existing TrueNAS Immich install.
https://www.reddit.com/r/immich/comments/1qc92m3/where_is_the_postgres_image_selection_field/

Questions:

  1. Is this a known issue with older TrueNAS Immich app/chart versions?
  2. Is there a supported way to expose or manually change postgres_image_selector from vectorchord_15_image to vectorchord_18_image?
  3. Should I edit ix_values.yaml manually, or is that unsafe?
  4. Is the recommended workaround to create a second Immich app instance pointing to the same host paths / pgData so it performs the PG15 → PG18 migration?

I have snapshots/backups and do not want to delete or recreate the existing app blindly. Any guidance on the safest upgrade path would be appreciated.

I'm going through the process of updating Immich from version 2.3.1 to latest (2.4.1 I believe as of 1/13/2026) and have run into an issue. The…

cerulean lanternBOT
#

:wave: Hey @balmy timber,

Thanks for reaching out to us. Please carefully read this message and follow the recommended actions. This will help us be more effective in our support effort and leave more time for building Immich immich.

References

#

Checklist

I have...

  1. :blue_square: verified I'm on the latest release(note that mobile app releases may take some time).
  2. :blue_square: read applicable release notes.
  3. :blue_square: reviewed the FAQs for known issues.
  4. :blue_square: reviewed Github for known issues.
  5. :blue_square: tried accessing Immich via local ip (without a custom reverse proxy).
  6. :blue_square: uploaded the relevant information (see below).
  7. :blue_square: tried an incognito window, disabled extensions, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable

(an item can be marked as "complete" by reacting with the appropriate number)

Information

In order to be able to effectively help you, we need you to provide clear information to show what the problem is. The exact details needed vary per case, but here is a list of things to consider:

  • Your docker-compose.yml and .env files.
  • Logs from all the containers and their status (see above).
  • All the troubleshooting steps you've tried so far.
  • Any recent changes you've made to Immich or your system.
  • Details about your system (both software/OS and hardware).
  • Details about your storage (filesystems, type of disks, output of commands like fdisk -l and df -h).
  • The version of the Immich server, mobile app, and other relevant pieces.
  • Any other information that you think might be relevant.

Please paste files and logs with proper code formatting, and especially avoid blurry screenshots.
Without the right information we can't work out what the problem is. Help us help you ;)

If this ticket can be closed you can use the /close command, and re-open it later if needed.

lament thistle
#

You missed the upgrade time window, they deprecated and removed the upgrade. TrueNAS unfortunately has an upgrade lifecycle that forces you to stay rather up to date all the time. There are some pinned posts in #truenas that might help. Should be #truenas message

balmy timber
#

Thanks, that makes sense. I checked the pinned PG15 → PG18 workaround, but I think my installation is older than the chart version that workaround assumes.

My current setup is:

  • TrueNAS SCALE: 24.10.2.2
  • Immich App Version: v1.141.1
  • TrueNAS chart/version: 1.9.24
  • Installed through TrueNAS Apps
  • Old storage migration already completed
  • Upgrade currently fails with:
ValidationErrors: [EINVAL] values.immich.postgres_image_selector: Invalid choice: vectorchord_15_image

The pinned guide says to edit:

postgres_upgrade_image:
  repository: ixsystems/postgres-upgrade
  tag: 1.2.1

or sometimes postgres_update_image, and change the tag to 1.1.11.

But in my file:

/mnt/.ix-apps/app_configs/immich/versions/1.9.24/ix_values.yaml

there is no postgres_upgrade_image, no postgres_update_image, and no Postgres image selector. I only have this:

images:
  pgvecto_image:
    repository: ghcr.io/immich-app/postgres
    tag: 15-vectorchord0.4.3-pgvectors0.2.0

Also, the TrueNAS app edit screen does not show a “Postgres Image (CAUTION)” dropdown, so I cannot switch PG15 → PG18 from the UI.

What is the safest path from this older chart version?

lament thistle
#

Also, the TrueNAS app edit screen does not show a “Postgres Image (CAUTION)” dropdown, so I cannot switch PG15 → PG18 from the UI.

Your version is probably even older than the upgrade timeframe which is why it does not show. @zealous frigate can you point in the right direction for this very old install?

zealous frigate
#

I keep delaying everything, but I'll, tomorrow is Immich day for me

zealous frigate
# balmy timber Hi, I need help with upgrading Immich on TrueNAS SCALE. Setup: * TrueNAS SCALE...
  1. A somewhat known issue with some specific Immich TrueNAS version
  2. There is but you'll need to convert to a custom app (whihc IIRC will require you to update to TrueNAS 25.04 minimum)
  3. That might actually work, but I would need to see your current file to know if that is something you could do
  4. Otherwise yes, but you would still need the ability to convert to a custom app as some values will have to be changed to update properly, more so that you're still on a <2.0 version of Immich
balmy timber
zealous frigate
#

Do you use ixVolumes or hostpath dataset for your data ?

balmy timber
#

hostpath

zealous frigate
#

Ok so the idea here is to install a "new immich" (you keep the old one) and reuse the same password as for your current Immich
you create two datasets for it (you will delete them later)
Then you convert this new Immich to a custom app

AFter that you share the custom yml here (remove the password when sharing the file)

#

Then I'll help you on what to change in this file to make this new immich upgrade the database of the old one

balmy timber
#

Got it. I’ll create a new temporary Immich app with two new temporary datasets, use the same DB password as my current Immich, then convert only this new app to a custom app. I won’t point it to the old production data/pgData yet.
After converting, I’ll share the custom YAML here with all passwords/secrets removed.

zealous frigate
#

Yes, we'll point to the old pgData manually while also changinc other parameters

balmy timber
#

I contacted you with the YAML via DM