@Tho is the fix already coming or i have to do something? i see on github that you are testing something u.u
Nope, you are trying the latest version. Could you send the logs?
not so fun fact: i tried to restore the backup and it said ‘‘you cannot restore you have karakeep already installed’’ so i uninstalled it without removing directory and also restored the backup and now i get
workers:
web:
For the restore, I guess it’s the issue with the nodejs mismatch. You could take a look at Restoring Jellyseerr from backup fails due to node.js version mismatch · Issue #78 · YunoHost-Apps/seerr_ynh · GitHub and adapt the nodejs version in the service file with the new one.
i never did any of this and karakeep has become my main use, i’ll update again to 33.1 and wait for the fix u,u
The most notable errors
no such column: "manualTierName" - should this be a string literal in single-quotes?
no such column: "lastSavedAt" - should this be a string literal in single-quotes?
Something is wrong with the database.
I have the exact same problem and error messages after an upgrade from karakeep to 0.33.1~ynh1. (Although I am on Yunohost 13.0.4 testing with Debian trixie.)
Also, the same columns seem to be missing.
A server error occurred. Reload to try again.
ERROR 3094453952
@ericg i thought you fixed it but apparently not (?)
Hello,
After making a full backup of karakeep, you can try upgrading from this version
yunohost app upgrade karakeep -u https://github.com/YunoHost-Apps/karakeep_ynh/tree/db_fix --force
NB: A previous full backup is really important since this upgrade will affect the existing database, so if it goes wrong and there’s no full backup…
it worked! thank you
btw now there is a new thing in the admin panel and it’s ‘‘browserless chrome’’ and it’s red; probably it matters only for the new single file features, the rest seems as usual
(not a problem to me but it’s still better to note it ig)
Ok: can you edit the /var/www/karakeep/.env and change
BROWSER_WEB_URL="http://localhost:9222"
to
BROWSER_WEB_URL="http://127.0.0.1:9222"
and finally
systemctl restart karakeep-*
thank you a loooooot!!!
Lorsque localhost est différent de 127.0.0.1 
… les joies de la coexistence ip4/ipv6 
Hello all,
I may have this same problem.
I upgraded Karakeep to 0.33.2~ynh1 and now no users can log in. They are not recognised, either by password login or api token. This suggests a database issue.
I notice the backup made via the web interface is only of core components.
@otm33 what is the CLI command to create a full backup?
I’ll try this approach, but want to make sure I have full backup beforehand, as per your advice.
Mmh… what do you mean ? Backup>Local>New Backup>System>unselect all>Apps>unselect_all>select Karakeep does not perform a full backup of karakeep ?
CLI : yunohost backup create --apps karakeep
Hi @otm33
No, when the backup command runs following the process you list, you can see the actions cycle through. Some of them say things like karakeep/x NOT BACKED UP because ‘’ is enabled. Several lines have this syntax.
I haven’t custom added anything to prevent a full backup running, which suggests: