You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I go to /kobo/[sync token]/v1/library/sync, I get a 500 internal server problem, and sync attempts on my kobo device give "sync failed" errors. I was using kobo sync without issue previously. A recent update to the linuxserver.io docker image seems to have triggered this error, but I don't understand the error messages well enough to know if it's more likely to be an issue with their image or calibre-web itself. A fresh reinstall has the same issue.
Also submitted upstream, where at least one other user of the linuxserver image is seeing the same issue:
"The server encountered an internal error and was unable to complete your request. There is an error in the application."
Environment
- OS: synology nas/docker
- Python version: not sure how to check
- Calibre-Web version: 0.6.20
- Docker container: linuxserver
- Special Hardware: synology nas
- Browser: n/a
installed via docker run
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
Is there an existing issue for this?
Current Behavior
When I go to /kobo/[sync token]/v1/library/sync, I get a 500 internal server problem, and sync attempts on my kobo device give "sync failed" errors. I was using kobo sync without issue previously. A recent update to the linuxserver.io docker image seems to have triggered this error, but I don't understand the error messages well enough to know if it's more likely to be an issue with their image or calibre-web itself. A fresh reinstall has the same issue.
Also submitted upstream, where at least one other user of the linuxserver image is seeing the same issue:
janeczku/calibre-web#2834
Expected Behavior
Kobo should sync with calibre-web
Steps To Reproduce
Steps to reproduce the behavior:
Environment
CPU architecture
x86-64
Docker creation
Container logs
The text was updated successfully, but these errors were encountered: