# Karakeep updates successfuly to v0.32.0 but fails to start
**URL:** https://forum.yunohost.org/t/karakeep-updates-successfuly-to-v0-32-0-but-fails-to-start/42262
**Category:** Support apps
**Tags:** karakeep, english
**Created:** [May 14, 2026, 6:33am UTC](https://forum.yunohost.org/t/karakeep-updates-successfuly-to-v0-32-0-but-fails-to-start/42262 "2026-05-14T06:33:41Z")
**Posts on this page:** 11
**Page:** 1
### Author:  [@partutokko](https://forum.yunohost.org/u/partutokko)
#### Post date: [May 14, 2026, 6:33am UTC](https://forum.yunohost.org/t/karakeep-updates-successfuly-to-v0-32-0-but-fails-to-start/42262/1 "2026-05-14T06:33:41Z")
**What app is this about, and its version** : Karakeep, v.0.32.0
**What YunoHost version are you running** : 12.1.39
**What type of hardware are you using** : VPS bought online
### Describe your issue
**What I’m trying to do**
I am attempting to update the Karakeep application from v0.31.0 to v0.32.0 on a YunoHost 12.1.39 (stable) system. Upgrade issues with Karakeep have occurred consistently with every update since v0.28.0 for me (not sure if related).
**What happens**
- **Update Process:** The update completes without errors, whether initiated via the YunoHost web-admin or CLI.
- **Post-Update Behavior:**
The application fails to start correctly.
The UI returns a `Internal Server Error` error when accessed.
The `karakeep-workers` service fails to start after the update.
The `karakeep-web` and `karakeep-browser` services appear to run correctly.
- **Rollback Attempt:**
Rolling back to v0.31.0 succeeds technically, but the application still does not start correctly afterward (services `karakeep-workers` and `karakeep-web` dead; `karakeep-browser` up and running).
**Troubleshooting already attempted**
Restarted the `karakeep-workers` service manually (no resolution).
Verified that the issue occurs regardless of the update method (web-admin or CLI).
**Additional Information**
I’ve been experiencing upgrade problems withe every upgrade since version 0.28.0.
If anyone has encountered similar issues or has insights into the `karakeep-workers` service failure, your guidance would be greatly appreciated. Let me know if further details or diagnostics are needed.
### Share relevant logs or error messages
**Update log:**
[https://paste.yunohost.org/raw/yezonojoqo](https://paste.yunohost.org/raw/yezonojoqo)
**`karakeep-workers` unit log:**
[https://paste.yunohost.org/raw/bevuculifo](https://paste.yunohost.org/raw/bevuculifo)
**Restore log:**
[https://paste.yunohost.org/raw/irisekikid](https://paste.yunohost.org/raw/irisekikid)
**After-rollback `karakeep-web` log:**
> **[hastebin](https://paste.yunohost.org/umodutunoj)**
**After-rollback `karakeep-workers` log:**
> **[hastebin](https://paste.yunohost.org/ubuwodiboc)**
---
### Author:  [@otm33](https://forum.yunohost.org/u/otm33)
#### Post date: [May 14, 2026, 8:23am UTC](https://forum.yunohost.org/t/karakeep-updates-successfuly-to-v0-32-0-but-fails-to-start/42262/2 "2026-05-14T08:23:42Z")
As a workaround, you can try this:
1. upgrade karakeep via CLI with the `--continue-on-failure` flag.
2. check the latest node.js 22 minor version installed on your server: `ls -l /opt/node_n/n/versions/node/` (22.22.3 I guess ?)
3. Replace 22.22.1 with this version in `/etc/systemd/system/karakeep-workers.service`
4. `systemctl daemon-reload`
5. `systemctl restart karakeep-workers`
---
### Author:  [@partutokko](https://forum.yunohost.org/u/partutokko)
#### Post date: [May 14, 2026, 9:18am UTC](https://forum.yunohost.org/t/karakeep-updates-successfuly-to-v0-32-0-but-fails-to-start/42262/3 "2026-05-14T09:18:44Z")
Did not work for 0.32.0 since:`ls -l /opt/node_n/n/versions/node/` returns **22.22.3** indeed
and **22.22.3** already in `/etc/systemd/system/karakeep-workers.service`, so nothing really to replace.
Your solution did the trick for the restored version though - so I’m back to 0.31.0.
**0.32.0** still doesn’t work.
---
### Author:  [@otm33](https://forum.yunohost.org/u/otm33)
#### Post date: [May 14, 2026, 9:30am UTC](https://forum.yunohost.org/t/karakeep-updates-successfuly-to-v0-32-0-but-fails-to-start/42262/4 "2026-05-14T09:30:39Z")
> [@partutokko](#):
>
> Did not work for 0.32.0 since:`ls -l /opt/node_n/n/versions/node/` returns **22.22.3** indeed
>
> and **22.22.3** already in `/etc/systemd/system/karakeep-workers.service`, so nothing really to replace.
I kind of suspected that, so this log here doesn’t seem to match the karakeep-workers service after the upgrade :
> [@partutokko](#):
>
> **Update log:**
>
> [https://paste.yunohost.org/raw/yezonojoqo](https://paste.yunohost.org/raw/yezonojoqo)
>
> **`karakeep-workers` unit log:**
>
> [https://paste.yunohost.org/raw/bevuculifo](https://paste.yunohost.org/raw/bevuculifo)
---
### Author:  [@orhtej2](https://forum.yunohost.org/u/orhtej2)
#### Post date: [May 14, 2026, 10:24am UTC](https://forum.yunohost.org/t/karakeep-updates-successfuly-to-v0-32-0-but-fails-to-start/42262/5 "2026-05-14T10:24:53Z")
what are the actual contents of `/var/www/karakeep/.env`, specifically the values of `INFERENCE_ENABLE_AUTO_TAGGING` and `INFERENCE_ENABLE_AUTO_SUMMARIZATION`. **don’t paste the whole file as it may contain secrets**.
Did you do any tweaking using config panel?
I’m asking because I just did fresh install of 0.31.0, upgraded to 0.32.0, changed settings using config panel and stuff still works 🤷
---
### Author:  [@partutokko](https://forum.yunohost.org/u/partutokko)
#### Post date: [May 14, 2026, 10:41am UTC](https://forum.yunohost.org/t/karakeep-updates-successfuly-to-v0-32-0-but-fails-to-start/42262/6 "2026-05-14T10:41:09Z")
Both are commented out:
```bash
# --- AI Features (Booleans) ---
#INFERENCE_ENABLE_AUTO_TAGGING=1
#INFERENCE_ENABLE_AUTO_SUMMARIZATION=0
```
---
### Author:  [@orhtej2](https://forum.yunohost.org/u/orhtej2)
#### Post date: [May 14, 2026, 11:22am UTC](https://forum.yunohost.org/t/karakeep-updates-successfuly-to-v0-32-0-but-fails-to-start/42262/7 "2026-05-14T11:22:28Z")
Can you uncomment them and change their respective values to `true` and `false` ?
---
### Author:  [@partutokko](https://forum.yunohost.org/u/partutokko)
#### Post date: [May 15, 2026, 5:23am UTC](https://forum.yunohost.org/t/karakeep-updates-successfuly-to-v0-32-0-but-fails-to-start/42262/8 "2026-05-15T05:23:36Z")
I replaced both values pre-upgrade. Upgrade went fine but it made no difference.
**Upgrade log:**
[https://paste.yunohost.org/raw/wevogimiho](https://paste.yunohost.org/raw/wevogimiho)
**Service logs:**
> **[hastebin](https://paste.yunohost.org/sumacinutu)**
Post upgrade I switched those values back to:
```auto
# --- AI Features (Booleans) ---
#INFERENCE_ENABLE_AUTO_TAGGING=1
#INFERENCE_ENABLE_AUTO_SUMMARIZATION=0
```
and restarted the unit. `karakeep-workers` started. I’m still getting `Internal Server Error` when trying to reach the app - despite the fact that all 3 apps services are up and running.
**`karakeep-web` logs:**
> **[hastebin](https://paste.yunohost.org/savamujafa)**
**`karakeep-browser` logs:**
> **[hastebin](https://paste.yunohost.org/imuhuwabip)**
**`karakeep-workers` logs:**
> **[hastebin](https://paste.yunohost.org/afoviyuyiw)**
---
### Author:  [@partutokko](https://forum.yunohost.org/u/partutokko)
#### Post date: [May 15, 2026, 5:43am UTC](https://forum.yunohost.org/t/karakeep-updates-successfuly-to-v0-32-0-but-fails-to-start/42262/9 "2026-05-15T05:43:11Z")
Ok, I think I resolved the issue: commenting out all the AI-related `.env` variables did the trick.
Not using any of these for the time being so not a big deal.
Thanks to all the involved.
---
### Author:  [@jarod5001](https://forum.yunohost.org/u/jarod5001)
#### Post date: [May 15, 2026, 11:19am UTC](https://forum.yunohost.org/t/karakeep-updates-successfuly-to-v0-32-0-but-fails-to-start/42262/10 "2026-05-15T11:19:10Z")
Config panel handles these keys.
Did you try to set them “false” instead of “0”
---
### Author:  [@system](https://forum.yunohost.org/u/system)
#### Post date: [May 30, 2026, 11:20am UTC](https://forum.yunohost.org/t/karakeep-updates-successfuly-to-v0-32-0-but-fails-to-start/42262/11 "2026-05-30T11:20:06Z")
This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.