Music app won't play webradio HTTPS stream

[BHuck74]

Hello everyone,

I used the Music app almost every day, mainly to listen to Webradios. Since migrating my Nextcloud instance to Docker with an Nginx Proxy Manager frontend, I can no longer play HTTPS streams. I get the following error: “Error while reading the URL: /apps/music/api/radio/10/stream”. HTTP streams work perfectly. I’ve followed the recommended configuration for running Nextcloud behind NPM, but without success. I’ve already spent hours trying to understand why these streams won’t play. This message is my last attempt before switching to another tool… Does anyone have an idea?

From within the nextcloud container, the following command seems ok :

curl -I https://icecast.radiofrance.fr/fipelectro-hifi.aac?id=radiofrance
HTTP/2 200 
server: nginx
date: Sat, 22 Nov 2025 14:05:43 GMT
content-type: audio/aac
icy-br: 192
ice-audio-info: channels=2;samplerate=48000;bitrate=192
icy-name: fipelectro-hifi.aac
icy-pub: 0
accept-ranges: none
cache-control: max-age=0, no-cache, no-store
expires: Sat, 22 Nov 2025 14:05:43 GMT
pragma: no-cache
access-control-allow-origin: *
access-control-expose-headers: Content-Type, icy-metaint, icy-br, ice-audio-info, icy-description, icy-genre, icy-name, icy-samplerate, icy-url

Cheers

[paulijar]

Have you tried HTTPS streams from any other provider? Because this https://icecast.radiofrance.fr/fipelectro-hifi.aac?id=radiofrance actually fails also on my setup when using the default "relayed play mode" i.e. relaying the radio stream through the Nextcloud server.

It took a while to figure out why this happens but it boiled down to one of the headers sent by that provider. The way the relaying works is that the Nextcloud server fetches the stream form the original source and then just sends it onward to the web client. Also all the HTTP headers are copied from the original response to the one sent to the client. But now, radiofrance.fr sends the header Transfer-Encoding: chunked which apparently isn't very typical. And somehow, writing this header to be sent to the web client confuses Nextcloud (or maybe Apache?) and the web client gets no response, whatsoever. But I didn't find any kind of error messages from anywhere.

I believe I can just exclude this one header when copying the response headers over and this should cause no issues. So this should get fixed to the next version of Music.

[paulijar]

@BHuck74 So have you been able to test other HTTPS radio streams? I'm wondering if you are only having the same issue which I found or if your system has also some other problem. For your convenience, here's one random HTTPS radio station which works without issues on my test setup with the latest released Music v2.4.1: https://wdr-1live-live.icecast.wdr.de/wdr/1live/live/mp3/128/stream.mp3.

[BHuck74]

Thank you so much for your answer and sorry for my late answer, I just missed the notification 🙄

I was pretty sure this could be linked to the proxy configuration but it seems not, since you experience the same behavior. This was also working fine on my previous Nextcloud instance, but perhaps the Music version wasn't the same (I can check but need to restart the old instance).

I will check with your sample stream at lunch time and let you now!

Have a great day.

[BHuck74]

Well, just tested with the https stream you provided, and it works like a charm. So I guess your analysis is true. Looks like french streams are coded by musicians 😂 But I still don't really understand why I was working on my previous instance.

Anyway, let me know if I can contribute by any means, and congrats for your work on this app.

[paulijar]

But I still don't really understand why I was working on my previous instance.

If you were using Music version older than 2.1.0 (released 2-Jan-2025), then it didn't relay the radio streams via the Nextcloud server but the front-end played them directly from the original source. This solution had its own problems, for example, it required lowering some security settings on the browser to be able to play any plain http streams.

But if your Music version wasn't this old, then it's possible that this problem to show up requires some specific version of Nextcloud or certain HTTP server configuration. What the Music app was doing here was kind of wrong but it's still a small mystery, why and how that caused this bug.

[BHuck74]

I couldn’t tell you, as I don’t know Nextcloud’s architecture in that level of detail. Before I migrated to Docker, Nextcloud was running in a jail on TrueNAS. Out of curiosity, I’ll restart the jail to check the version. In any case, thank you very much for your involvement.