-
-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Calibre not reachable - Closing connection with error: Error: WS was inactive for too long #121
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
Process inside Container:
Inspect:
|
I'm seeing the same issue using the latest container on my Synology NAS (DSM 7). Log snippet:
|
I had this issue with: Linuxserver.io version:- v6.14.1-ls207 Build-date:- 2023-03-15T22:02:06-05:00 but it seems to be fixed with: Linuxserver.io version:- v6.14.1-ls208 Build-date:- 2023-03-25T22:24:40-05:00 |
Can't confirm |
Command:
|
I also tried with the portainer templates from pi-hosted Still same error |
The latest one works for me, here is my setup: |
I think i'm waiting for the pull request #122 It looks good for that problem |
Irrelevant with new base |
Is there an existing issue for this?
Current Behavior
The calibre container throws the error "Closing connection with error: Error: WS was inactive for too long" and is not reachable over the ports
Expected Behavior
No response
Steps To Reproduce
Environment
CPU architecture
x86-64
Docker creation
docker run -d --rm --name test -p 8080:8080 --security-opt seccomp=unconfined lscr.io/linuxserver/calibre
Container logs
https://gist.github.com/DunklerPhoenix/9b32872e2b0cef17d65d4f50f33cdd46 (Too long for this field)
The text was updated successfully, but these errors were encountered: