Crawling job failed. Timeout exceeded

[nicduv]

Been using KaraKeep for a few months now without issue, but for the last few days I'm not able to get it to crawl when I add items. Here's the message I'm getting:

2025-06-28T17:43:37.510Z error: [Crawler][25649] Crawling job failed: Error: browserType.connect: Timeout 5000ms exceeded
browserType.connect: Timeout 5000ms exceeded
    at Proxy.connect (/app/apps/workers/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/playwright-extra/src/extra.ts:165:61)
    at async startBrowserInstance (/app/apps/workers/workers/crawlerWorker.ts:95:12)
    at async crawlPage (/app/apps/workers/workers/crawlerWorker.ts:283:15)
    at async crawlAndParseUrl (/app/apps/workers/workers/crawlerWorker.ts:668:14)
    at async runCrawler (/app/apps/workers/workers/crawlerWorker.ts:852:27)
    at async Object.run (/app/apps/workers/utils.ts:6:12)
    at async Runner.runOnce (/app/apps/workers/node_modules/.pnpm/[email protected]_@[email protected]_@[email protected][email protected][email protected]/node_modules/liteque/dist/runner.js:76:13)

As far as I can tell from the browserless logs, it is initiating and completing the crawl there without issue.

browserless.io:server:trace  Handling inbound WebSocket request on "/?token=XXXXXXXXXXXXXXX" +8m
  browserless.io:server:trace  Found matching WebSocket route handler "?(/),/chromium?(/)" +0ms
  browserless.io:server:trace  Authorizing WebSocket request to "http://0.0.0.0:3000/?token=XXXXXXXXXXXXXXX&launch=%7B%7D" +0ms
  browserless.io:server:trace  Validating route query-params with QUERY schema +0ms
  browserless.io:limiter:info  (Running: 0, Pending: 0) Adding to queue, max time allowed is 300,000ms  +8m
  browserless.io:limiter:info  (Running: 1, Pending: 0) Starting new job  +0ms
  browserless.io:ChromiumCDPWebSocketRoute:info 172.18.0.1 Starting new ChromiumCDP instance +0ms
  browserless.io:ChromiumCDPWebSocketRoute:info 172.18.0.1 ChromiumCDP got open port 46501 +1ms
  browserless.io:ChromiumCDPWebSocketRoute:info 172.18.0.1 {
  args: [
    '--remote-debugging-port=46501',
    '--no-sandbox',
    '--user-data-dir=/tmp/browserless-data-dirs/browserless-data-dir-716ebf2e-042e-4dab-a1dd-d684d5d4d9ca'
  ],
  executablePath: '/usr/local/bin/playwright-browsers/chromium-1179/chrome-linux/chrome'
} Launching ChromiumCDP Handler +0ms
  browserless.io:ChromiumCDPWebSocketRoute:info 172.18.0.1 ChromiumCDP is running on ws://127.0.0.1:46501/devtools/browser/4ece4bb1-9747-4773-ba4c-fa828a2e7945 +193ms
  browserless.io:router:trace  Running found WebSocket handler. +8m
  browserless.io:ChromiumCDPWebSocketRoute:info 172.18.0.1 Proxying http://0.0.0.0:3000/?token=XXXXXXXXXXXXXXX&launch=%7B%7D to ChromiumCDP ws://127.0.0.1:46501/devtools/browser/4ece4bb1-9747-4773-ba4c-fa828a2e7945 +0ms
  browserless.io:router:trace  WebSocket Request handler has finished. +107ms
  browserless.io:browser-manager:info  0 Client(s) are currently connected, Keep-until: 0, force: false +8m
  browserless.io:browser-manager:info  Closing browser session +0ms
  browserless.io:browser-manager:info  Deleting "/tmp/browserless-data-dirs/browserless-data-dir-716ebf2e-042e-4dab-a1dd-d684d5d4d9ca" user-data-dir and session from memory +0ms
  browserless.io:ChromiumCDPWebSocketRoute:info 172.18.0.1 Closing ChromiumCDP process and all listeners +107ms
  browserless.io:server:trace  Websocket connection complete +305ms
  browserless.io:limiter:info  Job has succeeded after 301ms of activity. +301ms
  browserless.io:limiter:info  (Running: 0, Pending: 0) All jobs complete.  +0ms
  browserless.io:browser-manager:info  Deleting data directory "/tmp/browserless-data-dirs/browserless-data-dir-716ebf2e-042e-4dab-a1dd-d684d5d4d9ca" +0ms

I've tried extending the timeout value for any of the variables that default to 5 seconds in the KaraKeep documentation, but still get the same Timeout 5000ms exceeded error.

Any ideas as to what could be causing this?

Thanks!

[nicduv]

I'm on Unraid and my container was using the old Hoarder repo. I changed to the Karakeep repo as noted by the template author below and everything is working again:

Due to trademark reasons, Hoarder has been rebranded to Karakeep. The good news is that both the old and new image repositories will continue receiving updates, so you don't have to update your template immediately.

However, if you'd like to switch to the new naming scheme, you can update your template by changing the repository line:

From:

ghcr.io/hoarder-app/hoarder:release

To:

ghcr.io/karakeep-app/karakeep:release

You do not have to change any other instance of the word Hoarder in the config, but you can if you would like to. Alternatively, you can stop your existing Hoarder container, use the new Karakeep template in CA and move your existing configuration to the new template.