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
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
(have slow internet connection
upload book with around 1gb size
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.
The text was updated successfully, but these errors were encountered:
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.
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.
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.
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
(have slow internet connection
upload book with around 1gb size
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
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.
The text was updated successfully, but these errors were encountered: