Tracks drop out partway through on Firefox only

[cortices]

On Firefox, tracks will sometimes stop part-way through and skip to the next track.

This is associated with the following error in JS console:

GET https://music.s0.is/rest/stream?id=<>&v=1.15.0&u=<>&s=<>&c=https://airsonic.netlify.app
[HTTP/2 416 Requested Range Not Satisfiable 3ms]
> Request headers:
> ...
> Range: bytes=37955211-

> Response headers:
> ...
> content-length: 33
> content-range: bytes */37955211

This obviously looks more like a bug with navidrome (my backend)... except that it only happens with airsonic-refix as frontend, and only on Firefox, not on Chrome.

After re-selecting the track that dropped out, it will usually play back fine until the end (or occasionally, drop out again, later). So it seems only related to an intermittent failure of the HTTP/2 websocket req for more audio chunk, with no real correlation to particular audio or metadata.

[khers]

I am seeing something similar (but also limited to firefox). If I select an entire album to play I will hear the first track but when the second starts I get the progress bar but no audio. If I select that track on the album, or seek using the progress bar it will start playing but at the next track boundary this will repeat (moving progress bar but no audio). Another possible clue is that the play button at the bottom of the page shows the pause bars on the first track but on the track boundary it switched to the play triangle. If I click that I get audio again.

[cortices]

Is there any way to disable HTTP/2 specifically on Netlify? I am going to deploy my own instance and see if the issue presents but the errors seem to be related to HTTP/2 transfers and content length issues, where Firefox aborts a connection if the Content-Length doesn't match received bytes, but Chrome does not.

[khannurien]

This happens to me too with gonic as a backend. The problem does not exist using airsonic-advanced as a backend.

Related: https://github.com/sentriz/gonic/issues/452

[QDucasse]

Hello, just iterating on this issue as it happens to me after a recent install using gonic as a backend. Gathering information from the different issues, the three main leads would be either a transcoding, tagging, or websocket failure?

Will update if I find a reproducible way to trigger the error! Thanks for the work!

[cortices]

Is there any way to disable HTTP/2 specifically on Netlify? I am going to deploy my own instance and see if the issue presents but the errors seem to be related to HTTP/2 transfers and content length issues, where Firefox aborts a connection if the Content-Length doesn't match received bytes, but Chrome does not.

Wanted to confirm: I've been running airsonic-refix self-hosted, with HTTP/2 disabled, and have not had this issue recur. Unclear still if it’s a Netlify-specific issue, or HTTP/2 in general.