July 11Jul 11 Hello,After the recent update, I am unable to access the webUI. I believe it has to do with my Postgres container needing to be migrated but was curious if someone could give me some guidance. I am using the Postgres12.5 container and receive the following error in the logs for Linkwarden:Error: P3009migrate found failed migrations in the target database, new migrations will not be applied. Read more about how to resolve migration issues in a production database: https://pris.ly/d/migrate-resolveThe 20260602155952_add_uuid_to_user_model migration started at 2026-07-11 06:01:53.950918 UTC failedAny help is greatly appreciated Edited July 11Jul 11 by obowan
July 13Jul 13 Hi,Same problem here:Error: P3009 migrate found failed migrations in the target database, new migrations will not be applied. Read more about how to resolve migration issues in a production database: https://pris.ly/d/migrate-resolve The 20260602155952_add_uuid_to_user_model migration started at 2026-07-11 06:27:11.411240 UTC failedEven tried older version (v2.14.1), but still the WebUI won't open.EDIT: rolled back to my 2026.07.11 backup (postgre and linkwarden), used v2.14.1 version and got it working again. Edited July 13Jul 13 by Lepo Arro
July 13Jul 13 Thank you @Lepo Arro for the response! Unfortunately I think I borked my db and even when reverting can't seem to get into the webUI. I think I'm going to have to go through the archive and manually add each bookmark. Thank you again!
July 27Jul 27 On 7/11/2026 at 9:44 PM, obowan said:Hello,After the recent update, I am unable to access the webUI. I believe it has to do with my Postgres container needing to be migrated but was curious if someone could give me some guidance. I am using the Postgres12.5 container and receive the following error in the logs for Linkwarden:Error: P3009migrate found failed migrations in the target database, new migrations will not be applied. Read more about how to resolve migration issues in a production database: https://pris.ly/d/migrate-resolveThe 20260602155952_add_uuid_to_user_model migration started at 2026-07-11 06:01:53.950918 UTC failedAny help is greatly appreciatedI got the same error shown in logs, and container doesn't start at all.I don't have time to debug it the next few days, so I'll leave everything as is and hope I don't need any bookmarks from the library.EDITOk, rollback to v2.14.1 and restore PostgreSQL and Linkwarden from backup works fine to get LW working again.In my case I believe PostgreSQL 12.5 container is to old for the LW v 2.16 but have to verify it in a calm moment.EDIT2Yes, upgrade to a PostgreSQL 18 did the trick. Now got a running Linkwarden 2.16. Edited July 30Jul 30 by shufflerror
Thursday at 09:24 PM3 days AI Tagging setting missing in PreferencesHello! This is a bug? that applies specifically to user of Unraid and the template for Linkwarden in the Community Apps store. I had the proper configuration to get AI Tagging working but the setting was missing from my webUI. Turns out to be a misconfiguration on the Unraid CA template itself. To fix, you need to edit the AI variable fields of the template. Both " NEXT_PUBLIC_OLLAMA_ENDPOINT_URL:" and "OLLAMA_MODEL:" Click edit and copy the contents of the "Name:" field into the "Key:" field. And that's it! Save yourself 2 hours of smashing head against keyboard to make it work.
Thursday at 09:24 PM3 days While I'm at it, there was a second template error that I had to fix in the "Data:" field. Originally it was "/mnt/cache/appdata/linkwarden". If you have the mover on Unraid configured to move data from the cache drive to your array, your preserved links (pdfs, screenshots, html file) will disappear. My option to fix was to amend the "Data:" field to say "/mnt/user/appdata/linkwarden". This allows Linkwarden to utilize the built in function of saving to the faster cache drive then moving to the array without breaking access to the preserved website formats.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.