jtechguru1993

The way id advise using it is using the multi select to mark anything you already have downloaded, as downloaded. I have a big library as well. I marked them all as downloaded. Unmarked the ones I needed. And then the database tracks from that. It doesn't scan a folder ahead of time for downloads parsed from any other instance.

Yeah the way the Community Application(the Apps) tab get it's information for icons etc is not actually stored with the docker container. They actually have to rescan my repo and at some point, I honestly don't know when, then it will grab the icon. I also don't know how that works with people who have already installed it.

I'm rolling the update today. I've been working on this since this morning. I really hope y'all like the refinements, and I have brought it up to current with the mainline Libation Project, at least as of September 21, 2026. Here's a summary: LibationWeb v0.5.0 — fixes "Content License denied" downloads (one manual step needed) Big update. The headline: it fixes the "Content License denied" error that's been breaking downloads for everyone. ⚠️ Updating alone won't fix downloads — there's a required step. The failures come from an upstream Audible change (Libation #2021): Audible stopped accepting the old device registration. The updated image has the fix, but each Audible account has to be re-registered. Update steps: Force Update the container (Docker tab → LibationWeb → Force Update). Open the web UI → Audible Accounts. On each account, click Re-authenticate (the key icon) and sign in again. (Removing + re-adding the account does the same thing.) Scan and download. Your library and settings are kept. If a download says "throttled" right after re-authenticating, that's Audible rate-limiting you from the earlier failed attempts — wait 24–48h and retry. Not a bug. Also new in 0.5.0: Re-authenticate button + a reminder banner for accounts that still need it Downloads page: Downloading / Downloaded / Failed filters and a Clear all failed button; a completed book auto-clears its own failed entries Serial download queue, scheduled library scans, and per-account auto-download (one book at a time, with a configurable pause, to stay off Audible's radar) First-run onboarding, better session management ("This device" + per-user sessions), and a What's new changelog right in Settings → About A round of dark-mode and UI fixes I have also rolled an update to fix the icon in unraid. The icon will not update by the container. That is handled by the unraid CA apps, which I have edited. The icon probably wont correct until it recrawls my github. I"ve made the changes that are required on my end for the icon, they will just take time to be processed.

I did not know this. It may have broken at some point and mine is cached already so mine is still loading. I'll add it to the list. I think I'll have the fixes in sooner than expected. I'll post here once they are in. Including the one you said. I'd like to say I appreciate the feedback. Really put a smile on my face. Additionally any problems you see, please call them out. I only realize something is wrong when it's not working or you guys tell me. I'm OCD so I really do pay attention to detail

You are correct. I noticed it about 2 weeks ago. I thought I kept rate limiting my account bc of the troubleshooting I was doing to the app. The remedy I am going to work on is bringing it up to date with current libation. I really do appreciate that you brought this to my attention. Know that I am taking it seriously, and I hope to have the fix ready within a week. It could be faster depending on how many changes there are, and if any require me to rebuild major components, either way I am on it.

unfortunately no. I had to build a custom backend to get libation as a cli, to act as the backend of a web application, and simultaneously use another part thats usually coupled with the gui program to pull together a cohesive project. Being honest the project is held together by easily broken chain links so to speak, and I am likely going to pin it to a version unless it is outright unusable. I was initially going to try and decouple them to allow for exactly what your asking for. The issue that I could not overcome was this caused the entire application to break, bc I cant anticipate the changes to the main project. I spent several hours this past weekend working on it, but for clarification none of that was to try and bring parity with the main libation project, at least as far as versioning information goes. It was definitely focused on refinement, bc there are quite a bit of issues present in the current release.

It should be automatic if its ticked. I too have noticed it is inconsistent among other issues. I am going to look into those though. I will try to push an update fixing this issue in particular, and then drill in on some of the other quirks ive noticed.

[Support] LibationWeb — Self-Hosted Web UI for Audible Audiobook Management LibationWeb is a Dockerized web interface for Libation (https://github.com/rmcrackan/Libation), the open-source Audible audiobook manager. It gives you a clean, mobile-friendly browser UI to manage your Audible library from Unraid — no desktop app required. Features: - Connect and scan one or more Audible accounts - Download and decrypt audiobooks directly to your Unraid share - Per-account auto-download after library scans - Multi-user support with 2FA, role-based permissions, and download caps - Session management and admin dashboard with logs and stats - PUID/PGID support for proper Unraid file permissions Docker Hub: jtechguru1993/libation-web:lates Source: https://github.com/jtechguru1/Libation/tree/web-ui-via-docker (fork) Support: All support is handled through this thread. questions, or feature requests here. This project is built on top of LibationCLI ndent community project, not affiliated with the original Libation project.