starred/audiobookshelf
1
0
Fork 0
mirror of https://github.com/advplyr/audiobookshelf.git synced 2026-05-30 23:40:40 +02:00
Code Issues 1.0k Packages Projects Releases 10 Wiki Activity

[Bug]: Upload Large file fails #2435

New Issue
Closed
opened 2026-04-25 00:07:06 +02:00 by adam · 6 comments
adam commented 2026-04-25 00:07:06 +02:00
Owner
Copy Link
Copy Source

Originally created by @Silther on GitHub (Dec 23, 2024).

What happened?

Often when uploading a new books via remote connection (Wireguard or reverse proxy caddy) the upload fails on large books.

But if i try to upload the same book via Wireguard and ssh (scp local server) it works without any issue.
It takes around 5-10 min but no connection error or something else occurs.

I am not completely sure if it only happens with additionally an slow internet connection, but it may be so.

What did you expect to happen?

Upload of large books (with slow internet) should work without any problems.

Steps to reproduce the issue

  1. (have slow internet connection
    image

  2. upload book with around 1gb size

  3. upload will take for ever (30+ min) and then fail

Audiobookshelf version

2.17.5

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

2024-12-23 14:33:18.067

INFO

[SocketAuthority] Socket Connected to /socket.io PAWRwANhuhUCS51SAAAx

2024-12-23 14:33:29.063

INFO

[SocketAuthority] Socket Connected to /socket.io QFKjlmjecIuku7c2AAAz

2024-12-23 14:35:10.046

INFO

[SocketAuthority] Socket Connected to /socket.io 6A-I8exjzx0YFZBcAAA1

2024-12-23 14:36:59.546

INFO

[SocketAuthority] Socket Connected to /socket.io Oqn5XDKuhzlJyQErAAA3

2024-12-23 14:37:44.512

INFO

[SocketAuthority] Socket Oqn5XDKuhzlJyQErAAA3 disconnected from client "yyy" after 44966ms (Reason: ping timeout)

2024-12-23 14:46:47.728

INFO

[SocketAuthority] Socket Connected to /socket.io xn21jhOWgeRm25l1AAA5

2024-12-23 14:57:29.297

INFO

[SocketAuthority] Socket Connected to /socket.io Gd7GqOz0huaQ53rRAAA7

2024-12-23 15:03:17.175

INFO

[SocketAuthority] Socket Gd7GqOz0huaQ53rRAAA7 disconnected from client "yyy" after 347878ms (Reason: ping timeout)

2024-12-23 15:03:28.481

ERROR

Invalid request, no files

2024-12-23 15:08:58.481

ERROR

Invalid request, no files

2024-12-23 15:14:28.484

ERROR

Invalid request, no files

2024-12-23 15:19:58.487

ERROR

Invalid request, no files

2024-12-23 15:24:54.324

INFO

[SocketAuthority] Socket xn21jhOWgeRm25l1AAA5 disconnected from client "yyy" after 2286596ms (Reason: ping timeout)

2024-12-23 15:25:28.483

ERROR

Invalid request, no files

2024-12-23 15:28:32.391

INFO

[SocketAuthority] Socket Connected to /socket.io saoX34mcVlIqtu3sAAA9

2024-12-23 15:28:32.595

INFO

[SocketAuthority] Socket Connected to /socket.io xnSHq-q2ux-8_8CFAABA

2024-12-23 15:28:32.737

INFO

[SocketAuthority] Socket Connected to /socket.io VGLihlfF00jRKh3LAABB

2024-12-23 15:28:33.211

INFO

[SocketAuthority] Socket Connected to /socket.io 9eXnbgzmBOVtLw5tAABD

2024-12-23 15:28:59.284

INFO

[SocketAuthority] Socket PAWRwANhuhUCS51SAAAx disconnected from client "zzz" after 3341218ms (Reason: ping timeout)

2024-12-23 15:29:10.999

INFO

[SocketAuthority] Socket 6A-I8exjzx0YFZBcAAA1 disconnected from client "zzz" after 3240954ms (Reason: ping timeout)

2024-12-23 15:29:11.635

INFO

[SocketAuthority] Socket QFKjlmjecIuku7c2AAAz disconnected from client "zzz" after 3342571ms (Reason: ping timeout)

2024-12-23 15:29:17.598

INFO

[SocketAuthority] Socket VGLihlfF00jRKh3LAABB disconnected from client "yyy" after 44860ms (Reason: ping timeout)

2024-12-23 15:29:30.240

ERROR

Invalid request, no files

Additional Notes

I have changed the file limit of caddy, but that did not change anything, wireguard should work non the less but it does not work too.

if i'm in the local net uploads to the server (via ip) work without problem.

Originally created by @Silther on GitHub (Dec 23, 2024). ### What happened? Often when uploading a new books via remote connection (Wireguard or reverse proxy caddy) the upload fails on large books. But if i try to upload the same book via Wireguard and ssh (scp local server) it works without any issue. It takes around 5-10 min but no connection error or something else occurs. I am not completely sure if it only happens with additionally an slow internet connection, but it may be so. ### What did you expect to happen? Upload of large books (with slow internet) should work without any problems. ### Steps to reproduce the issue 0. (have slow internet connection ![image](https://github.com/user-attachments/assets/939ea245-3a11-4fc8-8208-b203620c17d3) 1. upload book with around 1gb size 2. upload will take for ever (30+ min) and then fail ### Audiobookshelf version 2.17.5 ### 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 ```shell 2024-12-23 14:33:18.067 INFO [SocketAuthority] Socket Connected to /socket.io PAWRwANhuhUCS51SAAAx 2024-12-23 14:33:29.063 INFO [SocketAuthority] Socket Connected to /socket.io QFKjlmjecIuku7c2AAAz 2024-12-23 14:35:10.046 INFO [SocketAuthority] Socket Connected to /socket.io 6A-I8exjzx0YFZBcAAA1 2024-12-23 14:36:59.546 INFO [SocketAuthority] Socket Connected to /socket.io Oqn5XDKuhzlJyQErAAA3 2024-12-23 14:37:44.512 INFO [SocketAuthority] Socket Oqn5XDKuhzlJyQErAAA3 disconnected from client "yyy" after 44966ms (Reason: ping timeout) 2024-12-23 14:46:47.728 INFO [SocketAuthority] Socket Connected to /socket.io xn21jhOWgeRm25l1AAA5 2024-12-23 14:57:29.297 INFO [SocketAuthority] Socket Connected to /socket.io Gd7GqOz0huaQ53rRAAA7 2024-12-23 15:03:17.175 INFO [SocketAuthority] Socket Gd7GqOz0huaQ53rRAAA7 disconnected from client "yyy" after 347878ms (Reason: ping timeout) 2024-12-23 15:03:28.481 ERROR Invalid request, no files 2024-12-23 15:08:58.481 ERROR Invalid request, no files 2024-12-23 15:14:28.484 ERROR Invalid request, no files 2024-12-23 15:19:58.487 ERROR Invalid request, no files 2024-12-23 15:24:54.324 INFO [SocketAuthority] Socket xn21jhOWgeRm25l1AAA5 disconnected from client "yyy" after 2286596ms (Reason: ping timeout) 2024-12-23 15:25:28.483 ERROR Invalid request, no files 2024-12-23 15:28:32.391 INFO [SocketAuthority] Socket Connected to /socket.io saoX34mcVlIqtu3sAAA9 2024-12-23 15:28:32.595 INFO [SocketAuthority] Socket Connected to /socket.io xnSHq-q2ux-8_8CFAABA 2024-12-23 15:28:32.737 INFO [SocketAuthority] Socket Connected to /socket.io VGLihlfF00jRKh3LAABB 2024-12-23 15:28:33.211 INFO [SocketAuthority] Socket Connected to /socket.io 9eXnbgzmBOVtLw5tAABD 2024-12-23 15:28:59.284 INFO [SocketAuthority] Socket PAWRwANhuhUCS51SAAAx disconnected from client "zzz" after 3341218ms (Reason: ping timeout) 2024-12-23 15:29:10.999 INFO [SocketAuthority] Socket 6A-I8exjzx0YFZBcAAA1 disconnected from client "zzz" after 3240954ms (Reason: ping timeout) 2024-12-23 15:29:11.635 INFO [SocketAuthority] Socket QFKjlmjecIuku7c2AAAz disconnected from client "zzz" after 3342571ms (Reason: ping timeout) 2024-12-23 15:29:17.598 INFO [SocketAuthority] Socket VGLihlfF00jRKh3LAABB disconnected from client "yyy" after 44860ms (Reason: ping timeout) 2024-12-23 15:29:30.240 ERROR Invalid request, no files ``` ### Additional Notes I have changed the file limit of caddy, but that did not change anything, wireguard should work non the less but it does not work too. if i'm in the local net uploads to the server (via ip) work without problem.
adam added the bug label 2026-04-25 00:07:06 +02:00
adam closed this issue 2026-04-25 00:07:06 +02:00
adam commented 2026-04-25 00:07:06 +02:00
Author
Owner
Copy Link
Copy Source

@advplyr commented on GitHub (Dec 23, 2024):

Typically if it works locally then it is not an issue with Abs and it is a user network issue. That is because Abs doesn't have to know whether you are running locally or not, it is responding to requests the same.

That is not to say there is nothing we can improve or that it isn't possible there is an issue with Abs but to know if that is the case we need specific details on recreating the issue that doesn't require replicating your network setup.

@advplyr commented on GitHub (Dec 23, 2024): Typically if it works locally then it is not an issue with Abs and it is a user network issue. That is because Abs doesn't have to know whether you are running locally or not, it is responding to requests the same. That is not to say there is nothing we can improve or that it isn't possible there is an issue with Abs but to know if that is the case we need specific details on recreating the issue that doesn't require replicating your network setup.
adam commented 2026-04-25 00:07:07 +02:00
Author
Owner
Copy Link
Copy Source

@Silther commented on GitHub (Dec 23, 2024):

that's why i think it could have something todo with network speed and the way abs handles slow connections and timeouts.

if I connect my device via Wireguard, abs should behave the same as locally but it does not.
And uploading my books to the same server via ssh and wireguard works without problem.

will test it sometime again with an faster internet connection from remote.

@Silther commented on GitHub (Dec 23, 2024): that's why i think it could have something todo with network speed and the way abs handles slow connections and timeouts. if I connect my device via Wireguard, abs should behave the same as locally but it does not. And uploading my books to the same server via ssh and wireguard works without problem. will test it sometime again with an faster internet connection from remote.
adam commented 2026-04-25 00:07:07 +02:00
Author
Owner
Copy Link
Copy Source

@pwinnski commented on GitHub (Dec 23, 2024):

if I connect my device via Wireguard, abs should behave the same as locally but it does not.

The result is different, but ABS is behaving the same.

ABS has no idea whether you're connected locally or via reverse proxy or any other way. It always behaves the same way. So if you see different behavior, that is the result of the different network configuration, not a result of ABS doing anything different.

As advplyr said, it's possible ABS could handle uploads better than it does, but the first step would be to isolate what the issue actually is.

@pwinnski commented on GitHub (Dec 23, 2024): > if I connect my device via Wireguard, abs should behave the same as locally but it does not. The result is different, but ABS is behaving the same. ABS has no idea whether you're connected locally or via reverse proxy or any other way. It always behaves the same way. So if you see different behavior, that is the result of the different network configuration, not a result of ABS doing anything different. As advplyr said, it's possible ABS could handle uploads better than it does, but the first step would be to isolate what the issue actually is.
adam commented 2026-04-25 00:07:08 +02:00
Author
Owner
Copy Link
Copy Source

@SawkeeReemo commented on GitHub (Jan 5, 2025):

Is Cloudflare handling your DNS records? Because I use CF and they limit the upload amount to around 100mb for the free accounts. So that means when you try to upload via reverse proxy, with CF handing your DNS records, CF will cause the upload to fail. When I upload, I switch to my Tailscale connection to ABS and then I have no issues.

If you are not using Cloudflare, check with whoever manages your domain's DNS records.

@SawkeeReemo commented on GitHub (Jan 5, 2025): Is Cloudflare handling your DNS records? Because I use CF and they limit the upload amount to around 100mb for the free accounts. So that means when you try to upload via reverse proxy, with CF handing your DNS records, CF will cause the upload to fail. When I upload, I switch to my Tailscale connection to ABS and then I have no issues. If you are not using Cloudflare, check with whoever manages your domain's DNS records.
adam commented 2026-04-25 00:07:08 +02:00
Author
Owner
Copy Link
Copy Source

@Silther commented on GitHub (Jan 6, 2025):

Is Cloudflare handling your DNS records?

Yes, but I deactivated the cloudflare-proxy and for the rest I use Caddy as a reverse-proxy.
So there shouldn't be any limit right?

@Silther commented on GitHub (Jan 6, 2025): > Is Cloudflare handling your DNS records? Yes, but I deactivated the cloudflare-proxy and for the rest I use Caddy as a reverse-proxy. So there shouldn't be any limit right?
adam commented 2026-04-25 00:07:08 +02:00
Author
Owner
Copy Link
Copy Source

@Silther commented on GitHub (Jan 6, 2025):

I also uploaded a few 1+GB audiobooks with an faster internet connection (50Mbits) and with that it worked without any issue.

@Silther commented on GitHub (Jan 6, 2025): I also uploaded a few 1+GB audiobooks with an faster internet connection (50Mbits) and with that it worked without any issue.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
authentication
backlog
bug
chapter editor
config-issue
ebooks
encoding/embedding
enhancement
help wanted
listening sessions & progress
planned
possible plugin
progress sync
pull-request
Mirrored from GitHub Pull Request
 sorting/filtering/searching
unable to reproduce
upload
users & permissions
waiting
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam (Adam Melkus)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/audiobookshelf#2435
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?