#Error at very end of restoring DB backup

1 messages · Page 1 of 1 (latest)

mossy tiger
#

My setup is running on truenas scale 25.04.1, running the community app.

While updating from Immich v2.5.1 to v2.5.3 (v1.10.12 to v1.11.14 in truenas) via truenas UI, was running into errors from pgvecto_upgrade, causing it to crash.
Tried rolling back versions via truenas scale which seemingly corrupted my database as pgvecto started having missing file errors.

Created a new immich instance via community app with exact docker config, although pointing to newly created empty pgData dataset.

On the just created instance, went to onboarding, pressed restore backup, and when going through restore initially via onboarding UI, was running this postgres server response error
PostgresError: password authentication failed for user "postgres".

In logs of pgvecto, was complaining that "postgres" role does not exist.
I created said role manually, retried restore and (at least visually) got to about 95%.

Finally now left with this error from both pgvecto and in server containers:
PostgresError: password authentication failed for user "immich".

broken copperBOT
#

:wave: Hey @mossy tiger,

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. :ballot_box_with_check: verified I'm on the latest release(note that mobile app releases may take some time).
  2. :ballot_box_with_check: read applicable release notes.
  3. :ballot_box_with_check: reviewed the FAQs for known issues.
  4. :ballot_box_with_check: reviewed Github for known issues.
  5. :ballot_box_with_check: tried accessing Immich via local ip (without a custom reverse proxy).
  6. :ballot_box_with_check: uploaded the relevant information (see below).
  7. :ballot_box_with_check: 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.

mild spear
#

you will need to wait for the next release for truenas since it is a non standard deployment. either 2.5.4 or 2.6 version of immich

mossy tiger
#

would this change the probable cause in any way

broken copperBOT
wheat leaf
#

Your TrueNAS version is fine

#

You shouldn't have created a postgres user, and it won't change anything as TrueNAS deploys immich db with the "immich" user

#

So as Zeus said, you either have to wait for next release to restore with a db backup from GUI

#

Or we can do it with cli now, I can assist you with that if you want