Grimmory, previously known as BookLore, is a self-hosted application for managing your entire book collection in one place. Organize, read, annotate, sync across devices, and share without relying on third-party services.

For those migrating: You can either start a fresh instance, or copy your existing booklore's data path, and use the same MariaDB url and credentials.

So, I see a Booklore back on Github and Grimmory has been giving me some issues on upgrades like this evening again. (3.0)

Error:
Updated to 3.0.0 tonight on Unraid Docker and all library paths are showing as "inaccessible". Looked at the log files and this error comes up at restart:

2026-04-22T20:40:13.521-04:00 INFO 1 --- [booklore-api] [MessageBroker-1] o.s.w.s.c.WebSocketMessageBrokerStats : WebSocketSession[0 current WS(0)-HttpStream(0)-HttpPoll(0), 0 total, 0 closed abnormally (0 connect failure, 0 send limit, 0 transport error)], stompSubProtocol[processed CONNECT(0)-CONNECTED(0)-DISCONNECT(0)], stompBrokerRelay[null], inboundChannel[pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 0], outboundChannel[pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 0], sockJsScheduler[pool size = 2, active threads = 1, queued tasks = 0, completed tasks = 0]

And, this error comes up attempting to access library/books:
2026-04-22T20:44:57.573-04:00 ERROR 1 --- [booklore-api] [ async-14] o.b.s.library.LibraryProcessingService : Library path not accessible: /books/fiction

Are we changing back to Booklore again?

Update: I don't know what is going on but it looks like I lost or didn't have a share to the books collection.

Edited April 23Apr 23 by goldbondx