starred/karakeep

Fork 0

mirror of https://github.com/karakeep-app/karakeep.git synced 2026-04-26 00:16:03 +03:00

[GH-ISSUE #1685] Karakeep does not start after updating to 0.25.0 #1050

New issue

Closed

opened 2026-03-02 11:54:38 +03:00 by kerem · 1 comment

kerem commented

2026-03-02 11:54:38 +03:00

Owner

Originally created by @gcebollero on GitHub (Jun 28, 2025).
Original GitHub issue: https://github.com/karakeep-app/karakeep/issues/1685

Describe the Bug

After updating the docker container from 0.24.1 to 0.25.0, karakeep does not start, due to a "invalid url" on the migration job. Logs attached.

I have made a rollback and karakeep shows no URL errors.

Steps to Reproduce

Upgrade to 0.25.0
Open docker logs with docker logs karakeep

Expected Behaviour

Karakeep should be able to complete the migration job and start the service.

Screenshots or Additional Context

karakeep  | s6-rc: info: service s6rc-oneshot-runner: starting
karakeep  | s6-rc: info: service s6rc-oneshot-runner successfully started
karakeep  | s6-rc: info: service fix-attrs: starting
karakeep  | s6-rc: info: service init-db-migration: starting
karakeep  | Running db migration script
karakeep  | s6-rc: info: service fix-attrs successfully started
karakeep  | s6-rc: info: service legacy-cont-init: starting
karakeep  | s6-rc: info: service legacy-cont-init successfully started
karakeep  | /db_migrations/index.js:8309
karakeep  |         throw result.error;
karakeep  |         ^
karakeep  | 
karakeep  | ZodError: [
karakeep  |   {
karakeep  |     "validation": "url",
karakeep  |     "code": "invalid_string",
karakeep  |     "message": "Invalid url",
karakeep  |     "path": [
karakeep  |       "NEXTAUTH_URL"
karakeep  |     ]
karakeep  |   }
karakeep  | ]
karakeep  |     at get error (/db_migrations/index.js:8233:31)
karakeep  |     at ZodEffects.parse (/db_migrations/index.js:8309:22)
karakeep  |     at /db_migrations/index.js:13044:41
karakeep  |     at /db_migrations/index.js:13148:3
karakeep  |     at Object. (/db_migrations/index.js:13151:12)
karakeep  |     at Module._compile (node:internal/modules/cjs/loader:1730:14)
karakeep  |     at Object..js (node:internal/modules/cjs/loader:1895:10)
karakeep  |     at Module.load (node:internal/modules/cjs/loader:1465:32)
karakeep  |     at Function._load (node:internal/modules/cjs/loader:1282:12)
karakeep  |     at TracingChannel.traceSync (node:diagnostics_channel:322:14) {
karakeep  |   issues: [
karakeep  |     {
karakeep  |       validation: 'url',
karakeep  |       code: 'invalid_string',
karakeep  |       message: 'Invalid url',
karakeep  |       path: [ 'NEXTAUTH_URL' ]
karakeep  |     }
karakeep  |   ],
karakeep  |   addIssue: [Function (anonymous)],
karakeep  |   addIssues: [Function (anonymous)],
karakeep  |   errors: [
karakeep  |     {
karakeep  |       validation: 'url',
karakeep  |       code: 'invalid_string',
karakeep  |       message: 'Invalid url',
karakeep  |       path: [ 'NEXTAUTH_URL' ]
karakeep  |     }
karakeep  |   ]
karakeep  | }
karakeep  | 
karakeep  | Node.js v22.16.0
karakeep  | s6-rc: warning: unable to start service init-db-migration: command exited 1

Device Details

No response

Exact Karakeep Version

0.25.0

Have you checked the troubleshooting guide?

I have checked the troubleshooting guide and I haven't found a solution to my problem

Originally created by @gcebollero on GitHub (Jun 28, 2025). Original GitHub issue: https://github.com/karakeep-app/karakeep/issues/1685 ### Describe the Bug After updating the docker container from 0.24.1 to 0.25.0, karakeep does not start, due to a "invalid url" on the migration job. Logs attached. I have made a rollback and karakeep shows no URL errors. ### Steps to Reproduce 1. Upgrade to 0.25.0 2. Open docker logs with docker logs karakeep ### Expected Behaviour Karakeep should be able to complete the migration job and start the service. ### Screenshots or Additional Context ``` karakeep | s6-rc: info: service s6rc-oneshot-runner: starting karakeep | s6-rc: info: service s6rc-oneshot-runner successfully started karakeep | s6-rc: info: service fix-attrs: starting karakeep | s6-rc: info: service init-db-migration: starting karakeep | Running db migration script karakeep | s6-rc: info: service fix-attrs successfully started karakeep | s6-rc: info: service legacy-cont-init: starting karakeep | s6-rc: info: service legacy-cont-init successfully started karakeep | /db_migrations/index.js:8309 karakeep | throw result.error; karakeep | ^ karakeep | karakeep | ZodError: [ karakeep | { karakeep | "validation": "url", karakeep | "code": "invalid_string", karakeep | "message": "Invalid url", karakeep | "path": [ karakeep | "NEXTAUTH_URL" karakeep | ] karakeep | } karakeep | ] karakeep | at get error (/db_migrations/index.js:8233:31) karakeep | at ZodEffects.parse (/db_migrations/index.js:8309:22) karakeep | at /db_migrations/index.js:13044:41 karakeep | at /db_migrations/index.js:13148:3 karakeep | at Object. (/db_migrations/index.js:13151:12) karakeep | at Module._compile (node:internal/modules/cjs/loader:1730:14) karakeep | at Object..js (node:internal/modules/cjs/loader:1895:10) karakeep | at Module.load (node:internal/modules/cjs/loader:1465:32) karakeep | at Function._load (node:internal/modules/cjs/loader:1282:12) karakeep | at TracingChannel.traceSync (node:diagnostics_channel:322:14) { karakeep | issues: [ karakeep | { karakeep | validation: 'url', karakeep | code: 'invalid_string', karakeep | message: 'Invalid url', karakeep | path: [ 'NEXTAUTH_URL' ] karakeep | } karakeep | ], karakeep | addIssue: [Function (anonymous)], karakeep | addIssues: [Function (anonymous)], karakeep | errors: [ karakeep | { karakeep | validation: 'url', karakeep | code: 'invalid_string', karakeep | message: 'Invalid url', karakeep | path: [ 'NEXTAUTH_URL' ] karakeep | } karakeep | ] karakeep | } karakeep | karakeep | Node.js v22.16.0 karakeep | s6-rc: warning: unable to start service init-db-migration: command exited 1 ``` ### Device Details _No response_ ### Exact Karakeep Version 0.25.0 ### Have you checked the troubleshooting guide? - [x] I have checked the troubleshooting guide and I haven't found a solution to my problem

kerem

2026-03-02 11:54:38 +03:00

closed this issue
added the
bug

status/untriaged
labels

kerem commented

2026-03-02 11:54:39 +03:00

Author

Owner

@MohamedBassem commented on GitHub (Jun 28, 2025):

0.25 added a validation for what value you're using for NEXTAUTH_URL env variable because it's now used for rendering the urls of the public lists.

The error says that the value you're using for that env variable is not a correct url. If you fix that and do a docker compose up it'll start

@MohamedBassem commented on GitHub (Jun 28, 2025): 0.25 added a validation for what value you're using for NEXTAUTH_URL env variable because it's now used for rendering the urls of the public lists. The error says that the value you're using for that env variable is not a correct url. If you fix that and do a docker compose up it'll start

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/karakeep#1050

No description provided.

Rows
Columns