mirror of
https://github.com/advplyr/audiobookshelf.git
synced 2026-05-30 23:40:40 +02:00
[Bug]: [LibraryItemController] Failed to download file "{FILE}" Error: Request aborted #2465
Assignees
adam (Adam Melkus)
Clear assignees
adam (Adam Melkus)
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: starred/audiobookshelf#2465
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @AthenaShikata on GitHub (Jan 6, 2025).
What happened?
When the error occurs a popup appears in the browser saying "Progress is not being synced, restart playback." The chapter finishes, but won't continue. In the flappa mobile app, the chapter finishes, but won't continue. It may say it is unable to connect to the server, but usually not (I think it only says that after the issue resolves itself, but not 100%). The docker logs show this:
[2025-01-05 19:26:54.939] ERROR: [LibraryItemController] Failed to download file "{FILE}" Error: Request aborted at onaborted (/node_modules/express/lib/response.js:1052:15) at Immediate.<anonymous> (/node_modules/express/lib/response.js:1094:9) at process.processImmediate (node:internal/timers:483:21) { code: 'ECONNABORTED' }When I reload the page, I get stuck on the my.domain.com/login, but no login appears. When I try to log in on another device, the login gives an unknown error. Restarting the container or compose fixes the issue.
This issue persists for an arbitrary amount of time before fixing itself and doesn't happen for every chapter. Last night I had this happen for a couple chapters, but later that night I got through several chapters without issue. Today I've had it for every chapter so far. If I restart the container after the issue appears, the issue will reappear after a minute or two.
What did you expect to happen?
Continuous playback
Steps to reproduce the issue
Audiobookshelf version
v2.17.6 - v2.17.7
How are you running audiobookshelf?
Docker
What OS is your Audiobookshelf server hosted from?
Linux
If the issue is being seen in the UI, what browsers are you seeing the problem on?
None
Logs
Additional Notes
No response
@advplyr commented on GitHub (Jan 6, 2025):
When you say you reload the page and no login appears are you talking about the web client?
Where are you downloading the file from? The request being aborted could be the client and not the server
@AthenaShikata commented on GitHub (Jan 8, 2025):
I am talking about the web client. It's happening on multiple devices and clients so that leads me to believe it is a server error. The file is stored in the /audiobooks/{TITLE}/ folder in the mounted docker volume on my home server. I've been able to listen consistently when I connect directly over the network through the web client, but the "Progress is not being synced, restart playback." popup still appears, although no errors in the docker logs.
When I was checking the logs I found this error too. Similar butt different to the previous. I know it's not from me listening over the network because I was listening to a different book over the network than what appeared in the logs.
[2025-01-07 12:52:43.923] INFO: [LibraryItemController] User "{USER}" requested download for item "{TITLE}" file at "{FILE}" [2025-01-07 12:52:43.952] INFO: [LibraryItemController] Downloaded file "{FILE}" [2025-01-07 12:52:44.149] INFO: [LibraryItemController] User "{USER}" requested download for item "{TITLE}" file at "{FILE}" [2025-01-07 12:52:44.266] ERROR: [LibraryItemController] Failed to download file "{FILE}" Error: Request aborted at onaborted (/node_modules/express/lib/response.js:1052:15) at onfinish (/node_modules/express/lib/response.js:1088:50) at AsyncResource.runInAsyncScope (node:async_hooks:206:9) at listener (/node_modules/on-finished/index.js:170:15) at onFinish (/node_modules/on-finished/index.js:101:5) at callback (/node_modules/ee-first/index.js:55:10) at Socket.onevent (/node_modules/ee-first/index.js:93:5) at Socket.emit (node:events:530:35) at emitErrorNT (node:internal/streams/destroy:169:8) at emitErrorCloseNT (node:internal/streams/destroy:128:3) { code: 'ECONNABORTED' }@advplyr commented on GitHub (Jan 8, 2025):
Someone else mentioned they had this error on Discord and was also using Plappa. I think that error with file download specifically is something with how Plappa is downloading files.
If you can restart the server and only use the web client to listen that would be helpful to test. If you do that test make sure to be closed out of any mobile app client before restarting the server.
@AthenaShikata commented on GitHub (Jan 12, 2025):
I've been having other issues with my server and accessing the internet. I think this was causing the error I listed above. Reinstalled the os and it's working fine again. Thanks for your help!
@AthenaShikata commented on GitHub (Jan 13, 2025):
Never mind. Still seeing the error from my second comment in the logs and the "Progress not being synced, restart playback". However, it's not breaking the continuous playback when I listen through the proxied website like it was before. I think my other issues may have been causing this issue to be much worse than it normally is. The docker logs still just look like normal stuff until that one error pops up every chapter. Also in case this is relevant, the books I've been listening while this has been going on have each chapter in a different mp3 file. Sorry I closed this just to reopen it, but it hadn't happened in a long enough time that I thought it had resolved itself (which it kinda did, but not totally).
@advplyr commented on GitHub (Jan 20, 2025):
Are you using Plappa?
@AthenaShikata commented on GitHub (Jan 21, 2025):
I do use plappa, but this is primarily happening in the web client
@advplyr commented on GitHub (Jan 31, 2025):
Are you unable to download files using the web client?
So far this doesn't appear to be a bug to me. The client is aborting the request is what it is saying.
@AthenaShikata commented on GitHub (Feb 1, 2025):
I just downloaded the raw files of an entire audiobook from the web client. That isn't really the issue though. The issue is that the clients (both the web client and plappa) are aborting in the first place. Restarting the client resolves the issue temporarily, but it always returns. I don't know what else to call that other than a bug.
The previous logs were from the docker container, but I just found logs in the web client while messing with settings. Here are the logs from /metadata/logs:
[LibraryItemController] Failed to download file "{FILE}" Error: Request aborted at onaborted (/node_modules/express/lib/response.js:1052:15) at onfinish (/node_modules/express/lib/response.js:1088:50) at AsyncResource.runInAsyncScope (node:async_hooks:206:9) at listener (/node_modules/on-finished/index.js:170:15) at onFinish (/node_modules/on-finished/index.js:101:5) at callback (/node_modules/ee-first/index.js:55:10) at Socket.onevent (/node_modules/ee-first/index.js:93:5) at Socket.emit (node:events:530:35) at emitErrorNT (node:internal/streams/destroy:169:8) at emitErrorCloseNT (node:internal/streams/destroy:128:3) { code: 'ECONNABORTED' }I hope this new information helps.
@lukasz-karolewski commented on GitHub (May 13, 2025):
hi all, i have a similar issue, i hope will maybe help with finding the issue:
ERROR
[LibraryItemController] Failed to download file "" Error: write EPIPE at WriteWrap.onWriteComplete [as oncomplete] (node:internal/stream_base_commons:95:16) { errno: -32, code: 'EPIPE', syscall: 'write' }
ERROR
[LibraryItemController] Failed to download file "" Error: Request aborted at onaborted (/node_modules/express/lib/response.js:1052:15) at Immediate. (/node_modules/express/lib/response.js:1094:9) at process.processImmediate (node:internal/timers:483:21) { code: 'ECONNABORTED' }
I'm running on docker (2.21.0) with custom domain (pointing to private ip) and reverse proxy for https.
issue happens with Plappa only.
@mykpoz commented on GitHub (May 13, 2025):
I have similar issues running in Docker and accessing via plappa:
2025-05-13 08:33:09.655 ERROR [LibraryItemController] Failed to download file "" Error: write EPIPE at WriteWrap.onWriteComplete [as oncomplete] (node:internal/stream_base_commons:95:16) { errno: -32, code: 'EPIPE', syscall: 'write' }
2025-05-13 08:34:04.318 ERROR [LibraryItemController] Failed to download file "" Error: write EPIPE at WriteWrap.onWriteComplete [as oncomplete] (node:internal/stream_base_commons:95:16) { errno: -32, code: 'EPIPE', syscall: 'write' }
2025-05-13 08:34:55.735 ERROR [LibraryItemController] Failed to download file "" Error: write EPIPE at WriteWrap.onWriteComplete [as oncomplete] (node:internal/stream_base_commons:95:16) { errno: -32, code: 'EPIPE', syscall: 'write' }
2025-05-13 08:35:50.449 ERROR [LibraryItemController] Failed to download file "" Error: write EPIPE at WriteWrap.onWriteComplete [as oncomplete] (node:internal/stream_base_commons:95:16) { errno: -32, code: 'EPIPE', syscall: 'write' }
2025-05-13 08:36:45.296 ERROR [LibraryItemController] Failed to download file "" Error: write EPIPE at WriteWrap.onWriteComplete [as oncomplete] (node:internal/stream_base_commons:95:16) { errno: -32, code: 'EPIPE', syscall: 'write' }
@skridofly commented on GitHub (Feb 9, 2026):
@advplyr I am also experiencing the same issue or a really similar issue, but this time using the official audiobookshelf android application v0.11.0. The server is on version v2.32.1.
[LibraryItemController] Failed to download file "{file-path}" Error: Request aborted at onaborted (/app/node_modules/express/lib/response.js:1052:15) at onfinish (/app/node_modules/express/lib/response.js:1088:50) at AsyncResource.runInAsyncScope (node:async_hooks:206:9) at listener (/app/node_modules/on-finished/index.js:170:15) at onFinish (/app/node_modules/on-finished/index.js:101:5) at callback (/app/node_modules/ee-first/index.js:55:10) at Socket.onevent (/app/node_modules/ee-first/index.js:93:5) at Socket.emit (node:events:536:35) at emitErrorNT (node:internal/streams/destroy:169:8) at emitErrorCloseNT (node:internal/streams/destroy:128:3) { code: 'ECONNABORTED' }@Gangstrocity commented on GitHub (Feb 23, 2026):
This is the same thing that's been happening to me for months now. No clue what to do. It used to work perfectly. I've tried separate apps as well.