starred/karakeep

Fork 0

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

[GH-ISSUE #1604] d [TRPCError]: User settings not found #1001

New issue

Closed

opened 2026-03-02 11:54:17 +03:00 by kerem · 7 comments

kerem commented

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

Owner

Originally created by @varadins on GitHub (Jun 13, 2025).
Original GitHub issue: https://github.com/karakeep-app/karakeep/issues/1604

Describe the Bug

I had a previous install of Karakeep and I am now reinstalling in docker.

I have cleared all volumes, and images prior to this install.

Starting the container and attempting to access it results in

Application error: a server-side exception has occurred (see the server logs for more information). Digest: 4237581454

`s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service init-db-migration: starting
Running db migration script
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-db-migration successfully started
s6-rc: info: service svc-workers: starting
s6-rc: info: service svc-web: starting
s6-rc: info: service svc-workers successfully started
s6-rc: info: service svc-web successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
▲ Next.js 14.2.25

Local: http://localhost:3000
Network: http://0.0.0.0:3000

✓ Starting...
✓ Ready in 316ms
2025-06-13T13:20:18.270Z info: Workers version: 0.25.0
2025-06-13T13:20:18.301Z info: [crawler] Loading adblocker ...
2025-06-13T13:20:19.928Z info: [Crawler] Connecting to existing browser instance: http://chrome:9222
2025-06-13T13:20:19.929Z info: [Crawler] Successfully resolved IP address, new address: http://192.168.96.3:9222/
2025-06-13T13:20:20.007Z info: Starting crawler worker ...
2025-06-13T13:20:20.008Z info: Starting inference worker ...
2025-06-13T13:20:20.008Z info: Starting search indexing worker ...
2025-06-13T13:20:20.008Z info: Starting tidy assets worker ...
2025-06-13T13:20:20.009Z info: Starting video worker ...
2025-06-13T13:20:20.009Z info: Starting feed worker ...
2025-06-13T13:20:20.009Z info: Starting asset preprocessing worker ...
2025-06-13T13:20:20.010Z info: Starting webhook worker ...
2025-06-13T13:20:20.010Z info: Starting rule engine worker ...
d [TRPCError]: User settings not found
at /app/apps/web/.next/server/chunks/6815.js:1:41820
at async X.h.middlewares (/app/apps/web/.next/server/chunks/269.js:4:46337)
at async F (/app/apps/web/.next/server/chunks/269.js:7:68)
at async G (/app/apps/web/.next/server/chunks/269.js:4:45731)
at async F (/app/apps/web/.next/server/chunks/269.js:7:68)
at async F (/app/apps/web/.next/server/chunks/269.js:7:68)
at async F (/app/apps/web/.next/server/chunks/269.js:7:68)
at async G (/app/apps/web/.next/server/chunks/269.js:4:46537)
at async /app/apps/web/.next/server/chunks/269.js:7:5476
at async Promise.all (index 1) {
cause: undefined,
code: 'NOT_FOUND',
digest: '4237581454'
}`

Steps to Reproduce

Removed all volumes and images.
Installed via the following docker-compose.yml

GNU nano 7.2 docker-compose.yml
services:
web:
image: ghcr.io/karakeep-app/karakeep:${KARAKEEP_VERSION:-release}
restart: unless-stopped
volumes:
# By default, the data is stored in a docker volume called "data".
# If you want to mount a custom directory, change the volume mapping to:
# - /path/to/your/directory:/data
- data:/data
ports:
- 6002:3000
env_file:
- .env
environment:
MEILI_ADDR: http://meilisearch:7700
BROWSER_WEB_URL: http://chrome:9222
OPENAI_API_KEY: sk-proj-nLcEQOdzoC5A9tLfox2bWh9a-73Oye1FKmPpUDDOtgu1O19czplaoMqvO9Dr6zUQEJaaOzLKAdT3BlbkFJ1qJ0Vt0vpG_y9kNL3ftDOSy0DvSc1N13GCy4PRLrkYZvW2cDYq0loMb>
CRAWLER_NUM_WORKERS: 10
# You almost never want to change the value of the DATA_DIR variable.
# If you want to mount a custom directory, change the volume mapping above instead.
DATA_DIR: /data # DON'T CHANGE THIS
chrome:
image: gcr.io/zenika-hub/alpine-chrome:123
restart: unless-stopped
command:
- --no-sandbox
- --disable-gpu
- --disable-dev-shm-usage
- --remote-debugging-address=0.0.0.0
- --remote-debugging-port=9222
- --hide-scrollbars
meilisearch:
image: getmeili/meilisearch:v1.13.3
restart: unless-stopped
env_file:
- .env
environment:
MEILI_NO_ANALYTICS: "true"
volumes:
- meilisearch:/meili_data

volumes:
meilisearch:
data:

Expected Behaviour

I am not able to access gui - web page displays

`Application error: a server-side exception has occurred (see the server logs for more information).

Digest: 4237581454`

Screenshots or Additional Context

No response

Device Details

No response

Exact Karakeep Version

latest

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 @varadins on GitHub (Jun 13, 2025). Original GitHub issue: https://github.com/karakeep-app/karakeep/issues/1604 ### Describe the Bug I had a previous install of Karakeep and I am now reinstalling in docker. I have cleared all volumes, and images prior to this install. Starting the container and attempting to access it results in `Application error: a server-side exception has occurred (see the server logs for more information). Digest: 4237581454` `s6-rc: info: service s6rc-oneshot-runner: starting s6-rc: info: service s6rc-oneshot-runner successfully started s6-rc: info: service fix-attrs: starting s6-rc: info: service init-db-migration: starting Running db migration script s6-rc: info: service fix-attrs successfully started s6-rc: info: service legacy-cont-init: starting s6-rc: info: service legacy-cont-init successfully started s6-rc: info: service init-db-migration successfully started s6-rc: info: service svc-workers: starting s6-rc: info: service svc-web: starting s6-rc: info: service svc-workers successfully started s6-rc: info: service svc-web successfully started s6-rc: info: service legacy-services: starting s6-rc: info: service legacy-services successfully started ▲ Next.js 14.2.25 - Local: http://localhost:3000 - Network: http://0.0.0.0:3000 ✓ Starting... ✓ Ready in 316ms 2025-06-13T13:20:18.270Z info: Workers version: 0.25.0 2025-06-13T13:20:18.301Z info: [crawler] Loading adblocker ... 2025-06-13T13:20:19.928Z info: [Crawler] Connecting to existing browser instance: http://chrome:9222 2025-06-13T13:20:19.929Z info: [Crawler] Successfully resolved IP address, new address: http://192.168.96.3:9222/ 2025-06-13T13:20:20.007Z info: Starting crawler worker ... 2025-06-13T13:20:20.008Z info: Starting inference worker ... 2025-06-13T13:20:20.008Z info: Starting search indexing worker ... 2025-06-13T13:20:20.008Z info: Starting tidy assets worker ... 2025-06-13T13:20:20.009Z info: Starting video worker ... 2025-06-13T13:20:20.009Z info: Starting feed worker ... 2025-06-13T13:20:20.009Z info: Starting asset preprocessing worker ... 2025-06-13T13:20:20.010Z info: Starting webhook worker ... 2025-06-13T13:20:20.010Z info: Starting rule engine worker ... d [TRPCError]: User settings not found at /app/apps/web/.next/server/chunks/6815.js:1:41820 at async X.h.middlewares (/app/apps/web/.next/server/chunks/269.js:4:46337) at async F (/app/apps/web/.next/server/chunks/269.js:7:68) at async G (/app/apps/web/.next/server/chunks/269.js:4:45731) at async F (/app/apps/web/.next/server/chunks/269.js:7:68) at async F (/app/apps/web/.next/server/chunks/269.js:7:68) at async F (/app/apps/web/.next/server/chunks/269.js:7:68) at async G (/app/apps/web/.next/server/chunks/269.js:4:46537) at async /app/apps/web/.next/server/chunks/269.js:7:5476 at async Promise.all (index 1) { cause: undefined, code: 'NOT_FOUND', digest: '4237581454' }` ### Steps to Reproduce Removed all volumes and images. Installed via the following docker-compose.yml GNU nano 7.2 docker-compose.yml services: web: image: ghcr.io/karakeep-app/karakeep:${KARAKEEP_VERSION:-release} restart: unless-stopped volumes: # By default, the data is stored in a docker volume called "data". # If you want to mount a custom directory, change the volume mapping to: # - /path/to/your/directory:/data - data:/data ports: - 6002:3000 env_file: - .env environment: MEILI_ADDR: http://meilisearch:7700 BROWSER_WEB_URL: http://chrome:9222 OPENAI_API_KEY: sk-proj-nLcEQOdzoC5A9tLfox2bWh9a-73Oye1FKmPpUDDOtgu1O19czplaoMqvO9Dr6zUQEJaaOzLKAdT3BlbkFJ1qJ0Vt0vpG_y9kNL3ftDOSy0DvSc1N13GCy4PRLrkYZvW2cDYq0loMb> CRAWLER_NUM_WORKERS: 10 # You almost never want to change the value of the DATA_DIR variable. # If you want to mount a custom directory, change the volume mapping above instead. DATA_DIR: /data # DON'T CHANGE THIS chrome: image: gcr.io/zenika-hub/alpine-chrome:123 restart: unless-stopped command: - --no-sandbox - --disable-gpu - --disable-dev-shm-usage - --remote-debugging-address=0.0.0.0 - --remote-debugging-port=9222 - --hide-scrollbars meilisearch: image: getmeili/meilisearch:v1.13.3 restart: unless-stopped env_file: - .env environment: MEILI_NO_ANALYTICS: "true" volumes: - meilisearch:/meili_data volumes: meilisearch: data: ### Expected Behaviour I am not able to access gui - web page displays `Application error: a server-side exception has occurred (see the server logs for more information). Digest: 4237581454` ### Screenshots or Additional Context _No response_ ### Device Details _No response_ ### Exact Karakeep Version latest ### 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:17 +03:00

closed this issue
added the
bug

status/untriaged
labels

kerem commented

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

Author

Owner

@varadins commented on GitHub (Jun 13, 2025):

Cleared cookies and site data - working now. Okay to close.

@varadins commented on GitHub (Jun 13, 2025): Cleared cookies and site data - working now. Okay to close.

kerem commented

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

Author

Owner

@nickhelion commented on GitHub (Jun 21, 2025):

I have two distinct deployments, same issue on accessing the newly deployed. should be bug

@nickhelion commented on GitHub (Jun 21, 2025): I have two distinct deployments, same issue on accessing the newly deployed. should be bug

kerem commented

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

Author

Owner

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

@nickhelion are you using Oauth? If yes, it's a bug (https://github.com/karakeep-app/karakeep/issues/1583) and it's fixed in the nightly build.

@MohamedBassem commented on GitHub (Jun 21, 2025): @nickhelion are you using Oauth? If yes, it's a bug (https://github.com/karakeep-app/karakeep/issues/1583) and it's fixed in the nightly build.

kerem commented

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

Author

Owner

@nickhelion commented on GitHub (Jun 22, 2025):

@nickhelion are you using Oauth? If yes, it's a bug (#1583) and it's fixed in the nightly build.

No I don't, I use email&password, but I set the next auth related environment variables because the doc says they're required.

@nickhelion commented on GitHub (Jun 22, 2025): > [@nickhelion](https://github.com/nickhelion) are you using Oauth? If yes, it's a bug ([#1583](https://github.com/karakeep-app/karakeep/issues/1583)) and it's fixed in the nightly build. No I don't, I use email&password, but I set the next auth related environment variables because the doc says they're required.

kerem commented

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

Author

Owner

@calebsmithdev commented on GitHub (Jun 22, 2025):

Had a similar issue and clearing the cookies was my solution. Appreciate the detailed info!

@calebsmithdev commented on GitHub (Jun 22, 2025): Had a similar issue and clearing the cookies was my solution. Appreciate the detailed info!

kerem commented

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

Author

Owner

@nickhelion commented on GitHub (Jun 23, 2025):

I have two distinct deployments, same issue on accessing the newly deployed. should be bug

Update: the two deployments serves on the same ip with different ports. The issue only appears when accessed via ip:port
When I set a domain for the newly deployed one and access via domain, everything seems fine.

@nickhelion commented on GitHub (Jun 23, 2025): > I have two distinct deployments, same issue on accessing the newly deployed. should be bug Update: the two deployments serves on the same ip with different ports. The issue only appears when accessed via ip:port When I set a domain for the newly deployed one and access via domain, everything seems fine.

kerem commented

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

Author

Owner

@cavo789 commented on GitHub (Jul 14, 2025):

Same issue; same solution by clearing site data & cookies; thanks.

@cavo789 commented on GitHub (Jul 14, 2025): Same issue; same solution by clearing site data & cookies; thanks.

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#1001

No description provided.

Rows
Columns