Question 1

Why does the 'Save' button do nothing when editing or adding users in Calibre-Web-Automated?

Accepted Answer

This is a known bug affecting Safari and Orion browsers due to CSRF token handling. Workaround: Use Chrome or Firefox. The developers are working on a permanent fix. Track issue #986 for updates.

Question 2

Why does Calibre-Web show duplicate notifications but no duplicates found?

Accepted Answer

This is a known issue in Calibre-Web v4.0.6 where archived books can trigger false duplicate alerts. To fix, unarchive all books using SQLite commands:

```bash
sqlite3 /path/to/app.db "UPDATE archived_book SET is_archived = 0 WHERE user_id = 1;"
```

Adjust the database path and user_id as needed. After unarchiving, the duplicate notifications should stop.

Question 3

Why won't my Kobo download books after syncing with Calibre-Web Automated?

Accepted Answer

The download URLs sent to your Kobo device may be incorrect if you are using a reverse proxy. The sync service constructs URLs using the external port (default 8083) unless it detects an X-Forwarded-Host header. Fix: add 'X-Forwarded-Host $host' to your reverse proxy configuration (e.g., nginx) so the Kobo receives proper download links. If that does not work, set 'Server External Port' to 443 (or your reverse proxy's HTTPS port) under Basic Configuration > Enable Kobo Sync. If you are not using a reverse proxy, set the port to match your Calibre-Web port (e.g., 8083).

Question 4

How to fix 'setup_db failed: metadata.db not found at /calibre-library/#recycle/metadata.db' in Calibre-Web Docker?

Accepted Answer

This error occurs when the auto-library feature finds multiple metadata.db files (e.g., duplications inside a '#recycle' folder) and incorrectly picks a non‑primary copy. To fix: Remove any extra metadata.db files from subdirectories like '#recycle', ensuring only one valid metadata.db exists directly inside your library folder. If permissions were also an issue, run 'chown -R : /calibre-library' inside the container. After cleaning, restart the container to trigger a fresh auto‑detection.

Question 5

Why does KOreader on Android show 'Latest progress is coming from this device' when trying to sync from Kindle?

Accepted Answer

This occurs when the same book on different devices has different internal checksums. Delete the book from the Android device and re-download it from the same Calibre-Web OPDS catalog that the Kindle used. After re-fetching, the sync should work because the files will be identical. Alternatively, ensure both devices download the book at the same time without metadata changes in between.

Calibre-Web Automated

Core Features

What It Can't Do

Use Cases

Tags

Getting Started

Similar Projects