g8892

I did indeed attempt a restore but the Postgres extensions still prevented the DB from being read. So that didn't solve the problem, at least for my case. If I had known the issue all along I MIGHT have reverted back to an earlier working version of Postgres. However, the final solution I posted was also acceptable its the only solution I know for sure will work in my limited experience troubleshooting this issue.

Please direct me to the correct location if I am posting this in the wrong thread. I LOVE immich but I have been frustrated setting up paths to Postgres among other challenges. My immich container recently failed silently in the background after App Data Backup plugin applied an auto update. I have since turned off auto updates for immich and postgres. Here is an AI assisted summary of my 8 hour troubleshooting quest: Recovering an Immich Database After a PostgreSQL Vector Extension Failure on UnraidI recently ran into a difficult Immich upgrade issue that left the application stuck in a crash loop even though all photos were still present in the database. SymptomsImmich would not start. Logs contained errors similar to: could not access file "$libdir/vectors": No such file or directory The database still contained all assets and migrations, but the application crashed during startup. Root CauseThe PostgreSQL database had been created using the older vectors extension. After upgrading to the current Immich PostgreSQL image, the database contained: vector vchord but the old vectors extension library no longer existed. Two tables (face_search and smart_search) still depended on that obsolete extension, preventing Immich from starting. What Fixed ItInstead of rebuilding the library from scratch, I: Verified the database still contained all assets. Exported the database. Removed the obsolete vectors extension and its dependent search tables from the dump. Restored the dump into a clean PostgreSQL database using the official Immich PostgreSQL image. Confirmed the database contained the correct extensions: vector vchord Ran immich-admin schema-check, which identified the missing search tables and generated the SQL needed to recreate: face_search smart_search face_index clip_index Restarted Immich. The application started normally, and all photos, albums, users, and metadata were preserved. Lessons LearnedYour photo library may still be completely intact even if Immich won't start. Always verify the database before assuming it's corrupted. I spent WAY too long checking the DB. I should have moved on after a few targeted checks. Keep PostgreSQL on the official Immich-supported image and avoid mixing database images during upgrades. If immich-admin schema-check reports schema drift, read it carefully—it can generate the exact SQL needed to repair the database. Preventing This in the FutureBefore upgrading Immich: Make a full backup of your PostgreSQL database. Test major upgrades before deleting old backups. Disable automatic container updates (for example, in the Unraid Appdata Backup plugin or any auto-update tool. Automatic updates can leave you with a broken application before you've had a chance to verify compatibility or create a backup. A few minutes spent controlling updates is much better than hours recovering a production photo library.

I am also wondering the same thing.

Has anyone figured a way to connect Collabora to Nextcloud? Multiple users seem to be reporting the Collabora server breaking when following the Spaceinvaiderone tutorial referenced above. Nextcloud "Could not establish connection to the Collabora Online server." Thanks everyone!

This worked for me! THANK YOU for sharing that.