starred/karakeep

Fork 0

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

[GH-ISSUE #118] Search doesn't work #95

New issue

Closed

opened 2026-03-02 11:46:32 +03:00 by kerem · 8 comments

kerem commented

2026-03-02 11:46:32 +03:00

Owner

Originally created by @lucius346346 on GitHub (Apr 22, 2024).
Original GitHub issue: https://github.com/karakeep-app/karakeep/issues/118

Search doesn't seem to work for me in either web or mobile version.

App details:
App version: 0.12.2 (release) (latest release docker image from ghcr.io)

Steps to Reproduce:

Type any character in searchbox
"No bookmarks" shows up

Logs:
_hoarder-meilisearch-1_logs.txt

Originally created by @lucius346346 on GitHub (Apr 22, 2024). Original GitHub issue: https://github.com/karakeep-app/karakeep/issues/118 Search doesn't seem to work for me in either web or mobile version. **App details:** App version: 0.12.2 (release) (latest release docker image from ghcr.io) **Steps to Reproduce:** 1. Type any character in searchbox 2. "No bookmarks" shows up **Logs:** [_hoarder-meilisearch-1_logs.txt](https://github.com/MohamedBassem/hoarder-app/files/15059488/_hoarder-meilisearch-1_logs.txt)

kerem

2026-03-02 11:46:32 +03:00

closed this issue
added the
bug
label

kerem commented

2026-03-02 11:46:33 +03:00

Author

Owner

@MohamedBassem commented on GitHub (Apr 22, 2024):

Hey, this could indicate multiple things:

The worker container is failing to index in meilisearch. You should find errors in the worker container if that's the case.
You lost your meilisearch index (are you sure you have it on a persistent storage?)

If you broke your search index, you can trigger a reindex from the admin panel, it should be extremely fast. However, let's try to figure out what happened as well to prevent it from happening again.

@MohamedBassem commented on GitHub (Apr 22, 2024): Hey, this could indicate multiple things: 1. The worker container is failing to index in meilisearch. You should find errors in the worker container if that's the case. 2. You lost your meilisearch index (are you sure you have it on a persistent storage?) If you broke your search index, you can trigger a reindex from the admin panel, it should be extremely fast. However, let's try to figure out what happened as well to prevent it from happening again.

kerem commented

2026-03-02 11:46:33 +03:00

Author

Owner

@lucius346346 commented on GitHub (Apr 22, 2024):

It doesn't seem to be any error, only: 2024-04-22T08:09:15.063Z info: [search][542] Completed successfully
Index seems to exist:

Unfortunately, reindexing did nothing.

@lucius346346 commented on GitHub (Apr 22, 2024): 1. It doesn't seem to be any error, only: 2024-04-22T08:09:15.063Z info: [search][542] Completed successfully 2. Index seems to exist: ![image](https://github.com/MohamedBassem/hoarder-app/assets/43910504/1e7306cc-b4ee-492d-8058-3757205aa490) Unfortunately, reindexing did nothing.

kerem commented

2026-03-02 11:46:33 +03:00

Author

Owner

@MohamedBassem commented on GitHub (Apr 22, 2024):

Maybe the web container is failing to talk to meilisearch? Do you have anything special in your .env setup? Is the meilisearch master key and address correctly propagated to the web container?

@MohamedBassem commented on GitHub (Apr 22, 2024): Maybe the web container is failing to talk to meilisearch? Do you have anything special in your .env setup? Is the meilisearch master key and address correctly propagated to the web container?

kerem commented

2026-03-02 11:46:33 +03:00

Author

Owner

@lucius346346 commented on GitHub (Apr 22, 2024):

I didn't change much - only volume paths and default port.

Here's my config:
env.txt
docker-compose.txt

@lucius346346 commented on GitHub (Apr 22, 2024): I didn't change much - only volume paths and default port. Here's my config: [env.txt](https://github.com/MohamedBassem/hoarder-app/files/15059960/env.txt) [docker-compose.txt](https://github.com/MohamedBassem/hoarder-app/files/15059961/docker-compose.txt)

kerem commented

2026-03-02 11:46:34 +03:00

Author

Owner

@MohamedBassem commented on GitHub (Apr 22, 2024):

would you be interested in hopping onto discord for a more interactive debugging session? 😅

@MohamedBassem commented on GitHub (Apr 22, 2024): would you be interested in hopping onto discord for a more interactive debugging session? 😅

kerem commented

2026-03-02 11:46:34 +03:00

Author

Owner

@iweputo commented on GitHub (May 31, 2025):

I have the same issue now, cant Reindex through admin panel => "Fetch Failed", i havent changed directories of meilisearch and it has suddenly stopped working. What can it be?

@iweputo commented on GitHub (May 31, 2025): I have the same issue now, cant Reindex through admin panel => "Fetch Failed", i havent changed directories of meilisearch and it has suddenly stopped working. What can it be?

kerem commented

2026-03-02 11:46:34 +03:00

Author

Owner

@chicheese commented on GitHub (Jun 9, 2025):

Same. I checked Docker logs for meilisearch and am getting a
INFO HTTP request{method=GET host="meilisearch:7700" route=/indexes query_parameters= user_agent=node status_code=401 error=The Authorization header is missing. It must use the bearer authorization method.}

When I reindex through admin panel I get an error that also says "The Authorization header is missing. It must use the bearer authorization method."

Edit:
Never mind, I incorrectly configured my docker compose environment, forgot to add the MEILI_MASTER_KEY: variable. After adding that, redeploying the stack, and going to the Karakeep web admin panel and reindexing all bookmarks, works like a charm.

@chicheese commented on GitHub (Jun 9, 2025): Same. I checked Docker logs for meilisearch and am getting a `INFO HTTP request{method=GET host="meilisearch:7700" route=/indexes query_parameters= user_agent=node status_code=401 error=The Authorization header is missing. It must use the bearer authorization method.}` When I reindex through admin panel I get an error that also says "The Authorization header is missing. It must use the bearer authorization method." Edit: Never mind, I incorrectly configured my docker compose environment, forgot to add the `MEILI_MASTER_KEY:` variable. After adding that, redeploying the stack, and going to the Karakeep web admin panel and reindexing all bookmarks, works like a charm.

kerem commented

2026-03-02 11:46:34 +03:00

Author

Owner

@deepblue597 commented on GitHub (Oct 29, 2025):

Same issue here. Searching is not working and the logs of karakeep-web-app say

2025-10-29T16:54:21.966Z error: [search][8804] search job failed: MeiliSearchRequestError: Request to http://meilisearch:7700/indexes has failed
MeiliSearchRequestError: Request to http://meilisearch:7700/indexes has failed
    at file:///app/apps/workers/dist/plugins-search-meilisearch-CaCsu9Fv.js:279:10
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async HttpRequests.request (file:///app/apps/workers/dist/plugins-search-meilisearch-CaCsu9Fv.js:278:20)
    at async HttpRequests.get (file:///app/apps/workers/dist/plugins-search-meilisearch-CaCsu9Fv.js:307:10)
    at async MeiliSearch.getRawIndexes (file:///app/apps/workers/dist/plugins-search-meilisearch-CaCsu9Fv.js:1535:10)
    at async MeiliSearch.getIndexes (file:///app/apps/workers/dist/plugins-search-meilisearch-CaCsu9Fv.js:1520:22)
    at async MeiliSearchProvider.getClient (file:///app/apps/workers/dist/plugins-search-meilisearch-CaCsu9Fv.js:1972:19)
    at async PluginManager.getClient (file:///app/apps/workers/dist/plugins-Gk0CKWDA.js:12280:10)
    at async Object.runSearchIndexing [as run] (file:///app/apps/workers/dist/index.js:88661:23)
    at async Runner.runOnce (file:///app/apps/workers/node_modules/.pnpm/liteque@0.6.0_@opentelemetry+api@1.9.0_@types+better-sqlite3@7.6.13_@types+react@19.1.11_bett_q46iwo2f32qriczoxxudwy6mbu/node_modules/liteque/dist/index.js:229:4)
Error [TRPCError]: Request to http://meilisearch:7700/indexes has failed
    at <unknown> (.next/server/chunks/1413.js:3:834)
    at async w.request (.next/server/chunks/1413.js:3:810)
    at async w.get (.next/server/chunks/1413.js:3:1286)
    at async b.getRawIndexes (.next/server/chunks/1413.js:3:15652)
    at async b.getIndexes (.next/server/chunks/1413.js:3:15510)
    at async D.getClient (.next/server/chunks/1413.js:4:3134)
    at async o.getClient (.next/server/chunks/3504.js:1:3546)
    at async (.next/server/chunks/3014.js:1:20282)
    at async n.middlewares (.next/server/chunks/3487.js:28:6854) {
  code: 'INTERNAL_SERVER_ERROR',
  [cause]: Error [MeiliSearchRequestError]: Request to http://meilisearch:7700/indexes has failed
      at <unknown> (.next/server/chunks/1413.js:3:834)
      at async w.request (.next/server/chunks/1413.js:3:810)
      at async w.get (.next/server/chunks/1413.js:3:1286)
      at async b.getRawIndexes (.next/server/chunks/1413.js:3:15652)
      at async b.getIndexes (.next/server/chunks/1413.js:3:15510)
      at async D.getClient (.next/server/chunks/1413.js:4:3134)
      at async o.getClient (.next/server/chunks/3504.js:1:3546)
      at async (.next/server/chunks/3014.js:1:20282)
      at async n.middlewares (.next/server/chunks/3487.js:28:6854) {
    [cause]: TypeError: fetch failed
        at async w.request (.next/server/chunks/1413.js:3:810)
        at async w.get (.next/server/chunks/1413.js:3:1286)
        at async b.getRawIndexes (.next/server/chunks/1413.js:3:15652)
        at async b.getIndexes (.next/server/chunks/1413.js:3:15510)
        at async D.getClient (.next/server/chunks/1413.js:4:3134)
        at async o.getClient (.next/server/chunks/3504.js:1:3546)
        at async (.next/server/chunks/3014.js:1:20282)
        at async n.middlewares (.next/server/chunks/3487.js:28:6854) {
      [cause]: [Error [ConnectTimeoutError]: Connect Timeout Error (attempted address: meilisearch:7700, timeout: 10000ms)] {
        code: 'UND_ERR_CONNECT_TIMEOUT'
      }
    }
  }
}

@deepblue597 commented on GitHub (Oct 29, 2025): Same issue here. Searching is not working and the logs of karakeep-web-app say ``` 2025-10-29T16:54:21.966Z error: [search][8804] search job failed: MeiliSearchRequestError: Request to http://meilisearch:7700/indexes has failed MeiliSearchRequestError: Request to http://meilisearch:7700/indexes has failed at file:///app/apps/workers/dist/plugins-search-meilisearch-CaCsu9Fv.js:279:10 at process.processTicksAndRejections (node:internal/process/task_queues:105:5) at async HttpRequests.request (file:///app/apps/workers/dist/plugins-search-meilisearch-CaCsu9Fv.js:278:20) at async HttpRequests.get (file:///app/apps/workers/dist/plugins-search-meilisearch-CaCsu9Fv.js:307:10) at async MeiliSearch.getRawIndexes (file:///app/apps/workers/dist/plugins-search-meilisearch-CaCsu9Fv.js:1535:10) at async MeiliSearch.getIndexes (file:///app/apps/workers/dist/plugins-search-meilisearch-CaCsu9Fv.js:1520:22) at async MeiliSearchProvider.getClient (file:///app/apps/workers/dist/plugins-search-meilisearch-CaCsu9Fv.js:1972:19) at async PluginManager.getClient (file:///app/apps/workers/dist/plugins-Gk0CKWDA.js:12280:10) at async Object.runSearchIndexing [as run] (file:///app/apps/workers/dist/index.js:88661:23) at async Runner.runOnce (file:///app/apps/workers/node_modules/.pnpm/liteque@0.6.0_@opentelemetry+api@1.9.0_@types+better-sqlite3@7.6.13_@types+react@19.1.11_bett_q46iwo2f32qriczoxxudwy6mbu/node_modules/liteque/dist/index.js:229:4) Error [TRPCError]: Request to http://meilisearch:7700/indexes has failed at <unknown> (.next/server/chunks/1413.js:3:834) at async w.request (.next/server/chunks/1413.js:3:810) at async w.get (.next/server/chunks/1413.js:3:1286) at async b.getRawIndexes (.next/server/chunks/1413.js:3:15652) at async b.getIndexes (.next/server/chunks/1413.js:3:15510) at async D.getClient (.next/server/chunks/1413.js:4:3134) at async o.getClient (.next/server/chunks/3504.js:1:3546) at async (.next/server/chunks/3014.js:1:20282) at async n.middlewares (.next/server/chunks/3487.js:28:6854) { code: 'INTERNAL_SERVER_ERROR', [cause]: Error [MeiliSearchRequestError]: Request to http://meilisearch:7700/indexes has failed at <unknown> (.next/server/chunks/1413.js:3:834) at async w.request (.next/server/chunks/1413.js:3:810) at async w.get (.next/server/chunks/1413.js:3:1286) at async b.getRawIndexes (.next/server/chunks/1413.js:3:15652) at async b.getIndexes (.next/server/chunks/1413.js:3:15510) at async D.getClient (.next/server/chunks/1413.js:4:3134) at async o.getClient (.next/server/chunks/3504.js:1:3546) at async (.next/server/chunks/3014.js:1:20282) at async n.middlewares (.next/server/chunks/3487.js:28:6854) { [cause]: TypeError: fetch failed at async w.request (.next/server/chunks/1413.js:3:810) at async w.get (.next/server/chunks/1413.js:3:1286) at async b.getRawIndexes (.next/server/chunks/1413.js:3:15652) at async b.getIndexes (.next/server/chunks/1413.js:3:15510) at async D.getClient (.next/server/chunks/1413.js:4:3134) at async o.getClient (.next/server/chunks/3504.js:1:3546) at async (.next/server/chunks/3014.js:1:20282) at async n.middlewares (.next/server/chunks/3487.js:28:6854) { [cause]: [Error [ConnectTimeoutError]: Connect Timeout Error (attempted address: meilisearch:7700, timeout: 10000ms)] { code: 'UND_ERR_CONNECT_TIMEOUT' } } } } ```

kerem referenced this issue

2026-03-02 11:58:02 +03:00

[PR #95] [MERGED] feature: Recrawl failed links #1526

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

No description provided.

Rows
Columns