Issues syncing purchased books through the Kobo Store proxy

[an-ghinid]

What went wrong?

With the kobo store proxy enabled and kobo sync configured on my kobo libra 2, the following behaviour is observed:

For all grimmory managed books, sync is successful and works as expected

For all books purchased and synced via the Rakuten/Kobo store, sync fails with the following log snippet:

2026-05-08T18:59:03.869Z  WARN 1 --- [booklore-api] [omcat-handler-1] o.b.s.kobo.KoboInitializationService     : Unexpected response from Kobo /v1/initialization, fallback to noproxy
2026-05-08T18:59:06.201Z  INFO 1 --- [booklore-api] [mcat-handler-28] o.b.service.kobo.KoboEntitlementService  : Synced 2 tags to Kobo
2026-05-08T19:00:00.001Z  INFO 1 --- [booklore-api] [    scheduler-3] org.booklore.service.task.TaskService    : Executing cron-scheduled task: SYNC_LIBRARY_FILES
2026-05-08T19:00:00.063Z  INFO 1 --- [booklore-api] [    scheduler-3] org.booklore.service.task.TaskService    : SYNC_LIBRARY_FILES: Executing task
2026-05-08T19:00:00.064Z  INFO 1 --- [booklore-api] [    scheduler-3] o.booklore.task.tasks.LibraryScanTask    : SYNC_LIBRARY_FILES: Task started
2026-05-08T19:00:00.081Z  INFO 1 --- [booklore-api] [    scheduler-3] o.booklore.task.tasks.LibraryScanTask    : SYNC_LIBRARY_FILES: Rescanned library 'Books'
2026-05-08T19:00:00.081Z  INFO 1 --- [booklore-api] [    scheduler-3] o.booklore.task.tasks.LibraryScanTask    : SYNC_LIBRARY_FILES: Task completed. Duration: 17 ms
2026-05-08T19:00:00.749Z  INFO 1 --- [booklore-api] [        async-1] o.b.service.library.FileAsBookProcessor  : Finished processing library 'Books'
2026-05-08T19:00:00.754Z  INFO 1 --- [booklore-api] [        async-1] o.b.service.library.LibraryService       : Parsing task completed!
2026-05-08T19:07:11.402Z  WARN 1 --- [booklore-api] [cat-handler-251] o.b.s.kobo.KoboInitializationService     : Unexpected response from Kobo /v1/initialization, fallback to noproxy
2026-05-08T19:07:13.653Z  INFO 1 --- [booklore-api] [cat-handler-278] o.b.service.kobo.KoboEntitlementService  : Synced 2 tags to Kobo

All other aspects of sync are working correctly, and I can confirm that if I revert the kobo sync config changes and perform a regular sync via the default kobo store endpoint those purchased books show up as expected.

How can we reproduce it?

1. Purchase a book on the Kobo Store
2. Configure Kobo Sync on a Kobo device
3. Perform a sync
4. The purchased book will not be present as downloaded, and the book will still show as unpurchased in the in-device store page

What Build of Grimmory are you on?

Stable

Your setup

Grimmory version - 3.0.3
Install Method - Docker
Operating System - Linux
Browser - N/A

Screenshots or error messages (optional)

No response

Before submitting

• I've searched existing discussions and this hasn't been reported yet
• I've reviewed this report and have completed it as fully as I can

[imnotjames]

Can you set LOG_LEVEL to debug & do the same thing? I can't currently reproduce.

[an-ghinid]

I did a quick sign in/out of my kobo account on the device itself, re-setup the Kobo sync in the kobo's config itself and now my entitlements are showing up. Looking at my loki instance these 401s started appearing after the most recent firmware update on the Libra (approx two weeks ago and I hadn't bought a new book since then). I suspect something happened during that update which broke the auth on my kobo hence the 401. Looks like this wasn't actually a grimmory issue in the end (although this would be helpful to surface in the error messages if possible to make future troubleshooting a bit easier), thanks for your help!

[imnotjames]

I think it is a Grimmory issue that it's not passing the kobo auth along correctly.

[an-ghinid]

Interesting - the 401s are gone after I did a sign in/out in the kobo account settings itself and now I'm not seeing any unusual behaviour is the thing that confuses me then if there's also something happening grimmory side?

edit - or is it possible that I just have a temporary valid session from doing that and it's going to start 401ing again when that expires and the auth is no longer passed on?

[Originalme]

Interesting - the 401s are gone after I did a sign in/out in the kobo account settings itself and now I'm not seeing any unusual behaviour is the thing that confuses me then if there's also something happening grimmory side?

edit - or is it possible that I just have a temporary valid session from doing that and it's going to start 401ing again when that expires and the auth is no longer passed on?

Just curious, has the issue returned? My wife's Kobo has this issue, but I don't want her to have to reset it and reconfigure again if its not permanent.

[an-ghinid]

Interesting - the 401s are gone after I did a sign in/out in the kobo account settings itself and now I'm not seeing any unusual behaviour is the thing that confuses me then if there's also something happening grimmory side?

edit - or is it possible that I just have a temporary valid session from doing that and it's going to start 401ing again when that expires and the auth is no longer passed on?

Just curious, has the issue returned? My wife's Kobo has this issue, but I don't want her to have to reset it and reconfigure again if its not permanent.

Nope, not a single 401 since I reauthed, everything has been rock solid since and syncs without issue from what I've observed. Unsure if this was resolved in a release since or if the authentication resolved it. Possible it will still break again but no issues my end between my last post and now