starred/karakeep

Fork 0

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

[GH-ISSUE #1358] Crawling and AI tagging not working #870

New issue

Closed

opened 2026-03-02 11:53:23 +03:00 by kerem · 2 comments

kerem commented

2026-03-02 11:53:23 +03:00

Owner

Originally created by @varito18 on GitHub (May 5, 2025).
Original GitHub issue: https://github.com/karakeep-app/karakeep/issues/1358

Describe the Bug

I have setup Karakeep on my Synology NAS using Docker compose, but when I bookmark anything, the Crawler and Inference jobs are failing.

Here is an example of the error I am seeing:

5/5/2025 0:14	stdout	at async Runner.runOnce (/app/apps/workers/node_modules/.pnpm/liteque@0.3.2_better-sqlite3@11.3.0/node_modules/liteque/dist/runner.js:2:2656)

5/5/2025 0:14	stdout	at async Object.run (/app/apps/workers/utils.ts:2:940)

5/5/2025 0:14	stdout	at async runCrawler (/app/apps/workers/crawlerWorker.ts:3:13295)

5/5/2025 0:14	stdout	at async crawlAndParseUrl (/app/apps/workers/crawlerWorker.ts:3:9632)

5/5/2025 0:14	stdout	at async crawlPage (/app/apps/workers/crawlerWorker.ts:3:2104)

5/5/2025 0:14	stdout	at async CdpPage.goto (/app/apps/workers/node_modules/.pnpm/puppeteer-core@22.3.0/node_modules/puppeteer-core/lib/cjs/puppeteer/api/Page.js:590:20)

5/5/2025 0:14	stdout	at async CdpFrame.goto (/app/apps/workers/node_modules/.pnpm/puppeteer-core@22.3.0/node_modules/puppeteer-core/lib/cjs/puppeteer/cdp/Frame.js:137:25)

5/5/2025 0:14	stdout	at async Deferred.race (/app/apps/workers/node_modules/.pnpm/puppeteer-core@22.3.0/node_modules/puppeteer-core/lib/cjs/puppeteer/util/Deferred.js:36:20)

5/5/2025 0:14	stdout	at process.processTicksAndRejections (node:internal/process/task_queues:105:5)

5/5/2025 0:14	stdout	at navigate (/app/apps/workers/node_modules/.pnpm/puppeteer-core@22.3.0/node_modules/puppeteer-core/lib/cjs/puppeteer/cdp/Frame.js:171:27)

5/5/2025 0:14	stdout	Error: net::ERR_NAME_NOT_RESOLVED at https://nocodb.com/

5/5/2025 0:14	stdout	2025-05-04T22:14:16.093Z [31merror[39m: [Crawler][100] Crawling job failed: Error: net::ERR_NAME_NOT_RESOLVED at https://nocodb.com/

5/5/2025 0:14	stdout	2025-05-04T22:14:05.539Z [31merror[39m: [Crawler][100] Failed to determine the content-type for the url https://nocodb.com/: AbortError: The operation was aborted.

5/5/2025 0:14	stdout	2025-05-04T22:14:00.538Z [32minfo[39m: [Crawler][100] Attempting to determine the content-type for the url https://nocodb.com/

5/5/2025 0:14	stdout	2025-05-04T22:14:00.537Z [32minfo[39m: [Crawler][100] Will crawl "https://nocodb.com/" for link with id "yipl7760dv8k0m3c1vh93sya"

As for the AI tagging, I don't even see the requests hitting my OpenAI API.

Steps to Reproduce

This happens with any URL I try to bookmark.

My Docker Compose, as a reference:

services:
web:
container_name: Karakeep-WEB
image: ghcr.io/karakeep-app/karakeep:latest
restart: on-failure:5
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
- /volume1/docker/karakeep/data:/data:rw
ports:
- 3022:3000
environment:
MEILI_ADDR: http://meilisearch:7700
BROWSER_WEB_URL: http://chrome:9222
OPENAI_API_KEY: [OPENAI_KEY]
NEXTAUTH_SECRET: [NEXTAUTH_SECRET]
MEILI_MASTER_KEY: [MEILI_MASTER_KEY]
# 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:
container_name: Karakeep-CHROME
image: gcr.io/zenika-hub/alpine-chrome:123
restart: on-failure:5
command:
- --no-sandbox
- --disable-gpu
- --remote-debugging-address=0.0.0.0
- --remote-debugging-port=9222
- --hide-scrollbars
meilisearch:
container_name: Karakeep-MEILI
image: getmeili/meilisearch:v1.13.3
restart: on-failure:5
environment:
MEILI_NO_ANALYTICS: "true"
MEILI_MASTER_KEY: [MEILI_MASTER_KEY]
- /volume1/docker/karakeep/meili:/meili_data:rw

Expected Behaviour

The crawler and inference jobs should succeed.

Screenshots or Additional Context

No response

Device Details

Synology NAS DS920+

Exact Karakeep Version

0.24.1

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 @varito18 on GitHub (May 5, 2025). Original GitHub issue: https://github.com/karakeep-app/karakeep/issues/1358 ### Describe the Bug I have setup Karakeep on my Synology NAS using Docker compose, but when I bookmark anything, the Crawler and Inference jobs are failing. Here is an example of the error I am seeing: 5/5/2025 0:14 | stdout | at async Runner.runOnce (/app/apps/workers/node_modules/.pnpm/liteque@0.3.2_better-sqlite3@11.3.0/node_modules/liteque/dist/runner.js:2:2656) -- | -- | -- | | 5/5/2025 0:14 | stdout | at async Object.run (/app/apps/workers/utils.ts:2:940) | | 5/5/2025 0:14 | stdout | at async runCrawler (/app/apps/workers/crawlerWorker.ts:3:13295) | | 5/5/2025 0:14 | stdout | at async crawlAndParseUrl (/app/apps/workers/crawlerWorker.ts:3:9632) | | 5/5/2025 0:14 | stdout | at async crawlPage (/app/apps/workers/crawlerWorker.ts:3:2104) | | 5/5/2025 0:14 | stdout | at async CdpPage.goto (/app/apps/workers/node_modules/.pnpm/puppeteer-core@22.3.0/node_modules/puppeteer-core/lib/cjs/puppeteer/api/Page.js:590:20) | | 5/5/2025 0:14 | stdout | at async CdpFrame.goto (/app/apps/workers/node_modules/.pnpm/puppeteer-core@22.3.0/node_modules/puppeteer-core/lib/cjs/puppeteer/cdp/Frame.js:137:25) | | 5/5/2025 0:14 | stdout | at async Deferred.race (/app/apps/workers/node_modules/.pnpm/puppeteer-core@22.3.0/node_modules/puppeteer-core/lib/cjs/puppeteer/util/Deferred.js:36:20) | | 5/5/2025 0:14 | stdout | at process.processTicksAndRejections (node:internal/process/task_queues:105:5) | | 5/5/2025 0:14 | stdout | at navigate (/app/apps/workers/node_modules/.pnpm/puppeteer-core@22.3.0/node_modules/puppeteer-core/lib/cjs/puppeteer/cdp/Frame.js:171:27) | | 5/5/2025 0:14 | stdout | Error: net::ERR_NAME_NOT_RESOLVED at https://nocodb.com/ | | 5/5/2025 0:14 | stdout | 2025-05-04T22:14:16.093Z [31merror[39m: [Crawler][100] Crawling job failed: Error: net::ERR_NAME_NOT_RESOLVED at https://nocodb.com/ | | 5/5/2025 0:14 | stdout | 2025-05-04T22:14:05.539Z [31merror[39m: [Crawler][100] Failed to determine the content-type for the url https://nocodb.com/: AbortError: The operation was aborted. | | 5/5/2025 0:14 | stdout | 2025-05-04T22:14:00.538Z [32minfo[39m: [Crawler][100] Attempting to determine the content-type for the url https://nocodb.com/ | | 5/5/2025 0:14 | stdout | 2025-05-04T22:14:00.537Z [32minfo[39m: [Crawler][100] Will crawl "https://nocodb.com/" for link with id "yipl7760dv8k0m3c1vh93sya" As for the AI tagging, I don't even see the requests hitting my OpenAI API. ### Steps to Reproduce This happens with any URL I try to bookmark. My Docker Compose, as a reference: services: web: container_name: Karakeep-WEB image: ghcr.io/karakeep-app/karakeep:latest restart: on-failure:5 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 - /volume1/docker/karakeep/data:/data:rw ports: - 3022:3000 environment: MEILI_ADDR: http://meilisearch:7700 BROWSER_WEB_URL: http://chrome:9222 OPENAI_API_KEY: [OPENAI_KEY] NEXTAUTH_SECRET: [NEXTAUTH_SECRET] MEILI_MASTER_KEY: [MEILI_MASTER_KEY] # 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: container_name: Karakeep-CHROME image: gcr.io/zenika-hub/alpine-chrome:123 restart: on-failure:5 command: - --no-sandbox - --disable-gpu - --remote-debugging-address=0.0.0.0 - --remote-debugging-port=9222 - --hide-scrollbars meilisearch: container_name: Karakeep-MEILI image: getmeili/meilisearch:v1.13.3 restart: on-failure:5 environment: MEILI_NO_ANALYTICS: "true" MEILI_MASTER_KEY: [MEILI_MASTER_KEY] - /volume1/docker/karakeep/meili:/meili_data:rw ### Expected Behaviour The crawler and inference jobs should succeed. ### Screenshots or Additional Context _No response_ ### Device Details Synology NAS DS920+ ### Exact Karakeep Version 0.24.1 ### 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:53:23 +03:00

closed this issue
added the
bug

status/untriaged
labels

kerem commented

2026-03-02 11:53:24 +03:00

Author

Owner

@vhsdream commented on GitHub (May 5, 2025):

Error: net::ERR_NAME_NOT_RESOLVED likely means you have a networking issue; either your container is unable to access the internet, or your're having DNS issues. I would start there before doing anything else.

@vhsdream commented on GitHub (May 5, 2025): `Error: net::ERR_NAME_NOT_RESOLVED` likely means you have a networking issue; either your container is unable to access the internet, or your're having DNS issues. I would start there before doing anything else.

kerem commented

2026-03-02 11:53:24 +03:00

Author

Owner

@varito18 commented on GitHub (May 6, 2025):

Thank you. I moved the containers to a different existing bridge on my device and it worked well. So it looks like it was indeed a networking issue on my machine.

@varito18 commented on GitHub (May 6, 2025): Thank you. I moved the containers to a different existing bridge on my device and it worked well. So it looks like it was indeed a networking issue on my machine.

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

No description provided.

Rows
Columns