All links gone after update to v2.13.0

[dsp76]

Oh yes, so glad I found the thread and went back to package 1.18.1 to get back all our stuff.
Auto Update disabled for the moment...

[james]

Hello @linkwarden Users
Thanks for reporting this. We are looking into it.

[james]

I just installed Linkwarden Cloudron package version 1.18.1, added 2x links and updated the app to the latest version 1.19.0.
Still both links exist.
Could you please share some more details how your Linkwarden is used?
Are you using local accounts, the Cloudron Login, the Admin login or anything that could be useful to reproduce this issue?

[ari]

For me: Cloudron login, one admin user, public disabled. API calls failed after update, which tracks with the database being reset.

[ari]

Looking through recent issues, this one caught my eye given Cloudron login: https://github.com/linkwarden/linkwarden/issues/1422

[andreasdueren]

Weird, my links are still there. Using SSO

[fbartels]

I tried the upgrade today again. This is the log at the time of the upgrade:

Sep 29 10:35:34 box:tasks update 21502: {"percent":70,"message":"Creating container"}
Sep 29 10:35:34 box:apptask createContainer: creating container
Sep 29 10:35:36 box:shell apptask /usr/bin/sudo -S /home/yellowtent/box/src/scripts/configurelogrotate.sh add 4f552ab3-85b8-45de-b46a-05dc384d0c10 /tmp/4f552ab3-85b8-45de-b46a-05dc384d0c10.logrotate
Sep 29 10:35:36 box:apptask startApp: starting container
Sep 29 10:35:36 box:tasks update 21502: {"percent":90,"message":"Configuring reverse proxy"}
Sep 29 10:35:36 => Linkwarden configs
Sep 29 10:35:36 box:tasks update 21502: {"percent":100,"message":"Done"}
Sep 29 10:35:36 => Update configuration
Sep 29 10:35:36 ==> Setting up OIDC
Sep 29 10:35:36 box:taskworker Task took 103.25 seconds
Sep 29 10:35:36 box:tasks setCompleted - 21502: {"result":null,"error":null}
Sep 29 10:35:36 box:tasks update 21502: {"percent":100,"result":null,"error":null}
Sep 29 10:35:36 => Run database migration
Sep 29 10:35:37 yarn run v1.22.22
Sep 29 10:35:37 warning Skipping preferred cache folder "/usr/local/share/.cache/yarn" because it is not writable.
Sep 29 10:35:37 warning Selected the next writable cache folder in the list, will be "/tmp/.yarn-cache-0".
Sep 29 10:35:37 $ dotenv -- yarn workspace @linkwarden/prisma deploy
Sep 29 10:35:37 warning Cannot find a suitable global folder. Tried these: "/usr/local, /usr/local/share/.yarn"
Sep 29 10:35:37 warning Skipping preferred cache folder "/usr/local/share/.cache/yarn" because it is not writable.
Sep 29 10:35:37 warning Selected the next writable cache folder in the list, will be "/tmp/.yarn-cache-0".
Sep 29 10:35:38 warning package.json: "dependencies" has dependency "prisma" with range "^6.10.1" that collides with a dependency in "devDependencies" of the same name with version "^5.21.1"
Sep 29 10:35:38 warning Skipping preferred cache folder "/usr/local/share/.cache/yarn" because it is not writable.
Sep 29 10:35:38 warning Selected the next writable cache folder in the list, will be "/tmp/.yarn-cache-0".
Sep 29 10:35:38 $ prisma migrate deploy
Sep 29 10:35:38 warning Cannot find a suitable global folder. Tried these: "/usr/local, /usr/local/share/.yarn"
Sep 29 10:35:39 Prisma schema loaded from schema.prisma
Sep 29 10:35:39 Datasource "db": PostgreSQL database "db4f552ab385b845deb46a05dc384d0c10", schema "public" at "postgresql:5432"
Sep 29 10:35:39 2025-09-29T08:35:39Z
Sep 29 10:35:39 89 migrations found in prisma/migrations
Sep 29 10:35:39 2025-09-29T08:35:39Z
Sep 29 10:35:39 Applying migration `20250826181008_add_field_to_tags`
Sep 29 10:35:39 Applying migration `20250922133423_add_field_to_user`
Sep 29 10:35:39 2025-09-29T08:35:39Z
Sep 29 10:35:39 The following migration(s) have been applied:
Sep 29 10:35:39 2025-09-29T08:35:39Z
Sep 29 10:35:39 migrations/
Sep 29 10:35:39 └─ 20250826181008_add_field_to_tags/
Sep 29 10:35:39 └─ migration.sql
Sep 29 10:35:39 └─ 20250922133423_add_field_to_user/
Sep 29 10:35:39 └─ migration.sql
Sep 29 10:35:39 2025-09-29T08:35:39Z
Sep 29 10:35:39 All migrations have been successfully applied.
Sep 29 10:35:39 Done in 2.36s.
Sep 29 10:35:39 => Copying cache
Sep 29 10:35:40 => Healtheck error: Error: connect ECONNREFUSED 172.18.19.54:3000
Sep 29 10:35:41 => Ensure permissions
Sep 29 10:35:41 => Starting Linkwarden
Sep 29 10:35:41 yarn run v1.22.22
Sep 29 10:35:41 $ concurrently "dotenv -- yarn workspace @linkwarden/web start" "dotenv -- yarn workspace @linkwarden/worker start"
Sep 29 10:35:42 [1] $ tsx index.ts
Sep 29 10:35:42 [0] $ next start
Sep 29 10:35:43 [0] - ready started server on 0.0.0.0:3000, url: http://localhost:3000
Sep 29 10:35:47 [1] Initializing the worker...
Sep 29 10:35:47 [1] Starting RSS polling...
Sep 29 10:35:47 [1] Starting link processing...
Sep 29 10:35:48 [1] Processing new RSS feed items for This Week in Self-Hosted
Sep 29 10:35:50 [0] (node:192) [DEP0060] DeprecationWarning: The `util._extend` API is deprecated. Please use Object.assign() instead.
Sep 29 10:35:50 [0] (Use `node --trace-deprecation ...` to show where the warning was created)
Sep 29 10:36:02 [0] Warning: For production Image Optimization with Next.js, the optional 'sharp' package is strongly recommended. Run 'yarn add sharp', and Next.js will use it automatically for Image Optimization.
Sep 29 10:36:02 [0] Read more: https://nextjs.org/docs/messages/sharp-missing-in-production

And after logging in again the app was empty like with the previous update.

I then wanted to check the postgres database and this looks like it was wiped:

db4f552ab385b845deb46a05dc384d0c10=> /dt
db4f552ab385b845deb46a05dc384d0c10-> /d

So even though it says that it was able to apply the migrations to the database the database itself is empty afterwards. That was because of a syntax error on my end. I'm more of a MariaDB guy.

PS: also using sso and basically only using it with my first user. next to a few links I have setup a few rss sources in the app. the rss feeds are probably the most source for links since otherwise i hardly use linkwarden.

[luckow]

OIDC auth. same here: 0 links after the update.

[joseph]

I reproduced the issue. The issue seems to be that in old installations that started before the stable package, the email is not marked as verified. The API calls are failing with the error that email is not verified. To fix:

• Open a web terminal and click on the Postgres button on the top
• Then, run below. The email has to be replaced with the email in your linkwarden settings page:

UPDATE "User" SET "emailVerified"='2024-09-17 14:53:36.194' WHERE email='email@example.com';

That's it. Refresh linkwarden and things reappear.

[fbartels]

@joseph thank you. I can conform that after running the sql query the users do show up.

My observation with an empty database was because of a syntax error in my query.

[joseph]

@fbartels said in All links gone after update to v2.13.0:

My observation with an empty database was because of a syntax error in my query.

ha ha, those d* commands and the quoting of postgres always trips me (especially since I am on mysql a lot)!