mirror of
https://github.com/advplyr/audiobookshelf.git
synced 2026-05-30 23:40:40 +02:00
[Bug]: Long single file audiobooks don't start playback in Firefox #2910
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#2910
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 @PercyJW-2 on GitHub (Jul 21, 2025).
What happened?
When I try to start an audiobook that already has some progress into it it keeps loading. Apparently this issue only occurs when using Firefox or any Firefox derivative. I also took a look into the network communication within the debug tool, and it seems it is continuously downloading audiodata chunks.
What did you expect to happen?
Playback resumes at the location at which I stopped listening in the last session.
Steps to reproduce the issue
Audiobookshelf version
v2.26.1
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?
Firefox
Logs
Additional Notes
My Setup: Firefox browser on Arch-Linux, ABS (2.26.1) running inside docker behind reverse proxy. Each audiobook is stored as a single opus encoded file. For example one of the offending audiobooks is 22 hours long and the filesize is about 550 MB.
@Vito0912 commented on GitHub (Jul 21, 2025):
Try playing the file without ABS with the Firefox browser
@PercyJW-2 commented on GitHub (Jul 21, 2025):
That seems to work
@advplyr commented on GitHub (Jul 21, 2025):
Abs is just using the browsers audio player so if it plays standalone in the browser it should also play in Abs.
Have you tried without the reverse proxy?
Are you also testing in a mobile app? Not sure why the logs show you are using an old token on 2.26.1
@PercyJW-2 commented on GitHub (Jul 21, 2025):
The old token was probably from a discord RPC program (but now it should use the new tokens)
Also, the issue persists when I connect without the reverse proxy
@PercyJW-2 commented on GitHub (Jul 22, 2025):
Now after a while the loading stopped, but playback does not start. And the logs don't put out anything new, the last entry was:
@LeeThompson commented on GitHub (Jul 22, 2025):
I'm just throwing out some random things to try as a fellow user.
@PercyJW-2 commented on GitHub (Jul 22, 2025):
ffmpeg -i input_file.m4b -c:a libopus -b:a 60k output_file.opus)@PercyJW-2 commented on GitHub (Jul 22, 2025):
It seems to me that it tries to cache the whole file (at least until to the point I am listening) before starting playback and if that download takes too long it does not start playback
@nichwall commented on GitHub (Jul 22, 2025):
Two years ago another user spent a long time fighting opus in ogg containers in Firefox, specifically long ones. I'm not finding the exact conversation, but he ended up switching everything to webm to get around the issue in Firefox after multiple months of having the bug report open on the Firefox side.
He did also find it was specifically with files above a certain length, 10-12 hours sounds about right.
Edit: found the bug report, it specifically with Firefox on Linux.
https://bugzilla.mozilla.org/show_bug.cgi?id=1810378
@PercyJW-2 commented on GitHub (Jul 22, 2025):
Ah, I see. I'll think about what I will do about this.
Should this be closed due to not being a direct issue with ABS? Would it be an option to remux files during playback serverside? (I think Jellyfin does that for mkv files)
Also thanks for the help :D
@advplyr commented on GitHub (Jul 22, 2025):
Abs does automatically fallback to transcoding when the native browser audio player element throws an error.
https://github.com/advplyr/audiobookshelf/blob/878f0787ba39ff82f9d5b6b5b5bb397ec667f010/client/players/PlayerHandler.js#L121-L127
It seems like in this case the browser is not throwing an error though it is just stuck. Can you check the browser console logs to see if an error is being thrown?
@PercyJW-2 commented on GitHub (Jul 22, 2025):
This is printed into the browser console when loading finishes:
@advplyr commented on GitHub (Jul 22, 2025):
When the loading finishes what happens? Is the progress bar moving with no audio? Does the player show a pause button?
@PercyJW-2 commented on GitHub (Jul 22, 2025):
The player shows a pause button, but otherwise the UI is frozen, so neither the progress bar is moving nor the timestamp is changing.
@PercyJW-2 commented on GitHub (Jul 22, 2025):
Also the progress bar halts at the correct position
Screenshot of the player
@advplyr commented on GitHub (Jul 22, 2025):
If the browser audio player isn't throwing an error and reports that it is playing then I don't think we should try to handle this. You could add a comment to the Bugzilla report
@PercyJW-2 commented on GitHub (Jul 22, 2025):
Ok, I'll do that. Also, thanks for the work. Love the project