Oh, it looks like there are alternative versions! I'm using the browserless-v2 app from the unraid apps store (I'm not really sure the differences- I installed it ages ago, as also use it for changedetection.io).

The older unraid "browserless" app uses the docker image browserless/chrome, which hasn't been updated in over a year so you are probably best to change. The v2 version uses ghcr.io/browserless/chromium which is still maintained.

38 minutes ago, traynier said:

The older unraid "browserless" app uses the docker image browserless/chrome, which hasn't been updated in over a year so you are probably best to change. The v2 version uses ghcr.io/browserless/chromium which is still maintained.

Ah yeah I just figured that out as you did and updated my original post. Thanks for the help!

Hi,

i'm getting constant errors regarding Meilisearch (inside the Karakeep logs):
2025-07-23T08:43:32.883Z error: [search][36634] search job failed: MeiliSearchTimeOutError: timeout of 5000ms has exceeded on process 16983 when waiting a task to be resolved.

• Meilisearch is properly configured with a br0 adress (no conflicts) on port 7700 and properly configured in Karakeep pointing at the same spot using the correct Meili Master Key.

• Meilisearch is working properly inside the Karakeep webUI, parsing correct content hits.

I'm out of ideas getting rid of that error appearing constantly.

Edited July 23, 2025Jul 23 by Gekko

Hi All,

I seem to be running in to issues with the browserless part of the setup.

I have move to the browserless v2 image, but I think the only issue is the karakeep url for the browserless connection.

here is my Karakeep setup

and here is my Browserless-v2 setup

When I add an Url I get the following message when I look at the page within Karakeep UI "Failed to fetch link content ..."

Any ideas would be great. I will try and get logs but a bit new to unraid and docker.

Hi @Slothy2406

You need to add the port on the BROWSER_WEBSOCKET_URL - i.e. ws://[IP]:[PORT]/chromium/playwright?token=[TOKEN]

I'm not sure on your IP setup, but it will likely be port 3000 or 3012, so ws://192.168.100.241:3000/chromium/playwright?.....

You also have a typo later on in that URL - its playwright, not playwrite

Edited July 25, 2025Jul 25 by traynier

4 hours ago, Slothy2406 said:

Hi All,

I seem to be running in to issues with the browserless part of the setup.

I have move to the browserless v2 image, but I think the only issue is the karakeep url for the browserless connection.

4 hours ago, Slothy2406 said:

I had those problems, too and for me it's working when

• browserless-v2 is running the port 3012, but in the

• Karakeep docker, i needed this port to point at 3000

• in the Karakeep browser address you need to specify everything like this: ws://x.x.x.x:3000/chromium/playwright?token=XXX

Hope, it helps

Just went through similar issues - it worked fine for a while but recently noticed karakeep was not successfully pulling and traced it back to a timeout communicating with browserless. The solution was to switch to CA's "browserless-v2" template and replacing the URL used in karakeep's template with ws://[IP]:[PORT]/chromium/playwright?token=[TOKEN]

I'd recommend a note be added to the top of this thread if it's editable, and the docs @ https://docs.karakeep.app/Installation/unraid be updated to specify "browserless-v2" instead of just "browserless" to help anyone who encounters this issue in the future.

I'll also add the previous commenter mentioned using browserless-v2's internal port # in the karakeep config. I did not need to do that, using 3012 in karakeep worked as it should.

Edited July 27, 2025Jul 27 by jpresson

I run Ollama in my local network and would like to give AI the task to tag and to summarize my bookmarks. Tagging works without flaws, but when initializing summaries, my config is full with the message that Karakeep skips this, cause it's "disabled in the config":

2025-07-27T16:25:04.586Z info: [inference][51955] Skipping summarization job for bookmark with id "lmjmui92kycaozckqzxkjyjd" because it's disabled in the config.
2025-07-27T16:25:04.586Z info: [inference][51955] Completed successfully

I don't have any clue, where and how this is disabled, as there is not any option anywhere. It's not in the docker parameters, it's not anywhere in the backend, i really don't know how to turn ON summarization. Can anyone help me?

17 hours ago, jpresson said:

Just went through similar issues - it worked fine for a while but recently noticed karakeep was not successfully pulling and traced it back to a timeout communicating with browserless. The solution was to switch to CA's "browserless-v2" template and replacing the URL used in karakeep's template with ws://[IP]:[PORT]/chromium/playwright?token=[TOKEN]

I'd recommend a note be added to the top of this thread if it's editable, and the docs @ https://docs.karakeep.app/Installation/unraid be updated to specify "browserless-v2" instead of just "browserless" to help anyone who encounters this issue in the future.

I'll also add the previous commenter mentioned using browserless-v2's internal port # in the karakeep config. I did not need to do that, using 3012 in karakeep worked as it should.

Editing he URL to add playwright worked for me. Thank you

On 7/27/2025 at 8:46 AM, jpresson said:

Just went through similar issues - it worked fine for a while but recently noticed karakeep was not successfully pulling and traced it back to a timeout communicating with browserless. The solution was to switch to CA's "browserless-v2" template and replacing the URL used in karakeep's template with ws://[IP]:[PORT]/chromium/playwright?token=[TOKEN]

I'd recommend a note be added to the top of this thread if it's editable, and the docs @ https://docs.karakeep.app/Installation/unraid be updated to specify "browserless-v2" instead of just "browserless" to help anyone who encounters this issue in the future.

I'll also add the previous commenter mentioned using browserless-v2's internal port # in the karakeep config. I did not need to do that, using 3012 in karakeep worked as it should.

Same, just piling on to hopefully help others find this easier than I did.

On 7/22/2025 at 8:46 AM, traynier said:

To get it to work for Karakeep 0.26 change the BROWSER_WEBSOCKET_URL to ws://[IP]:[PORT]/chromium/playwright?token=[TOKEN]

i.e. insert "/playwright"

See https://github.com/karakeep-app/karakeep/issues/1758

thx, that did the trick for me as well on unraid with karakeep 0.26.0 and browserless-v2

DISABLE_SIGNUPS - where should it go?

And is it:

DISABLE_SIGNUPS=no

for it to work?

Edited August 12, 2025Aug 12 by JGNiDK

I deployed Karakeep manually using Docker Compose on Unraid, set a custom port, and added the missing NEXTAUTH_SECRET. No template needed. It worked perfectly.

Run this in the terminal:

mkdir -p ~/karakeep/docker

cd ~/karakeep/docker

Create/enter the .env file:

nano .env

paste this code in the .env file :

# Postgres

POSTGRES_USER=karakeep

POSTGRES_PASSWORD=karakeep

POSTGRES_DB=karakeep

# Karakeep

DATABASE_URL=postgres://karakeep:karakeep@db:5432/karakeep

REDIS_URL=redis://redis:6379

MEILI_URL=http://meilisearch:7700

WORKER_URL=http://worker:3001

NEXTAUTH_SECRET=supersecurekarakeepsecret

# Worker

BROWSERLESS_URL=http://browserless:3000

Create/enter the docker-compose.yml file:

nano docker-compose.yml

paste this code in the Docker-composer.yml file:

GNU nano 8.4 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:

- 3890:3000

env_file:

- .env

environment:

MEILI_ADDR: http://meilisearch:7700

BROWSER_WEB_URL: http://chrome:9222

# OPENAI_API_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:

image: gcr.io/zenika-hub/alpine-chrome:124

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

Finally run:

docker compose up -d --build

Edited August 19, 2025Aug 19 by Rewrap

On 7/27/2025 at 10:46 PM, jpresson said:

Just went through similar issues - it worked fine for a while but recently noticed karakeep was not successfully pulling and traced it back to a timeout communicating with browserless. The solution was to switch to CA's "browserless-v2" template and replacing the URL used in karakeep's template with ws://[IP]:[PORT]/chromium/playwright?token=[TOKEN]

I'd recommend a note be added to the top of this thread if it's editable, and the docs @ https://docs.karakeep.app/Installation/unraid be updated to specify "browserless-v2" instead of just "browserless" to help anyone who encounters this issue in the future.

I'll also add the previous commenter mentioned using browserless-v2's internal port # in the karakeep config. I did not need to do that, using 3012 in karakeep worked as it should.

I've added information about using browserless-v2 to the main post and updated the template to specify Browserless-v2 in the description.

I was wondering why browserless-v2 kept spinning up a job every ~10s and realised it was caused by karakeep. Why might this be happening?

edit: Ah, might be the BROWSER_CONNECT_ONDEMAND which defaults to false (in which case karakeep tries to keep a connection open)

Edited September 25, 2025Sep 25 by jayphen

On 7/22/2025 at 2:46 AM, traynier said:

To get it to work for Karakeep 0.26 change the BROWSER_WEBSOCKET_URL to ws://[IP]:[PORT]/chromium/playwright?token=[TOKEN]

i.e. insert "/playwright"

See https://github.com/karakeep-app/karakeep/issues/1758

yep this worked for me - using browserlessv2 and unraid 7.1.4

Curious if anyone has any suggestions for using stealth mode with Browserless? Of the 8 initial links I've added to Karakeep, 2 don't finish, the logs end with Stored the screenshot as assetId:xxx, but stay blank and 1 is blocked by Cloudflare. I also tried using the hosted version of Browserless to use the /chromium/stealth URL but that seems to have to connection issues with Karakeep (I assume because it uses CDP protocol instead of native Playwright).

Thanks!

So, after wasting two days trying to install Karakeep from the CA Store under unRAID (yes, including Browserless v2 and Meilisearch), and with the Karakeep log now working (nearly) perfectly, I've noticed that while tags are being created, but no AI functions (summary), no screenshots, nothing like that! ChatGTP says it's simply not implemented in the CA app! Is that possible? What's your experience, and what did you do to get crawling working? My log and the Browserless log are attached...

THANKS!browserless-log.txtkarakeep-log.txt

Edited January 11Jan 11 by Trustwbc

10 minutes ago, Trustwbc said:

- <ws connect error> ws://karakeep-browserless:3000/chromium/playwright connect ECONNREFUSED 172.18.0.3:3000

Karakeep isn't connecting to Browserless. If you haven't set a token in the Browserless config, try removing '?token=' and everything after in the Browserless Address variable.

I've just installed Karakeep, browserless-v2 and Meilisearch, but I'm running into what I think is one final issue. I'm using the "latest" tags for Karakeep and browserless-v2, but the Karakeep logs are saying there's a version mismatch for Playwright whenever I try to save a page.

From Karakeep logs:
Playwright version mismatch:

- server version: v1.59

- client version: v1.58

I see that Karakeep updated the Playwright dependency to 1.58.2 with v0.31.0, but browserless-v2 uses Playwright v1.59 according to this log message.
Are others having this problem? Is there something I should do differently with my install?
Please let me know if there's any info I can provide to help diagnose.

On 4/2/2026 at 4:54 AM, Bradwheat said:

I've just installed Karakeep, browserless-v2 and Meilisearch, but I'm running into what I think is one final issue. I'm using the "latest" tags for Karakeep and browserless-v2, but the Karakeep logs are saying there's a version mismatch for Playwright whenever I try to save a page.

From Karakeep logs:
Playwright version mismatch:

- server version: v1.59

- client version: v1.58

I see that Karakeep updated the Playwright dependency to 1.58.2 with v0.31.0, but browserless-v2 uses Playwright v1.59 according to this log message.
Are others having this problem? Is there something I should do differently with my install?
Please let me know if there's any info I can provide to help diagnose.

Have the absolute same issue, Karakeep stopped working for me after 2 years of flawless use. The dev's decision to make such a breaking change makes me just speechless, it renders the use of browserless absolutely useless, cause the playwright dependencies of Karakeep/browserless can't match. The project gets flooded by weird design decisions lately and here we are: i don't understand how someone could make such a stupid decision once again.

Temporaly fix:

In Unraid, go to DOCKER, click the browserless-v2 text link and change the repository to "ghcr.io/browserless/chromium:v2.44.0", this way the Karakeep deployment will work again untill an official fix is out!

Edited April 3Apr 3 by Gekko

On 4/3/2026 at 3:16 PM, Gekko said:

Temporaly fix:

In Unraid, go to DOCKER, click the browserless-v2 text link and change the repository to "ghcr.io/browserless/chromium:v2.44.0", this way the Karakeep deployment will work again untill an official fix is out!

Thank you for this! I thought I was taking crazy pills. Seems to be working now.

Excellent! I wasn't sure how to determine which browserless-v2 release had the old Playwright version, so the temporary fix above helped me.