Rinse FM and Kool FM streams not working in Roon (ref#TX44LM)

Support
1

Hi! What’s not quite right with Roon?

· None of the above quite fits

None of the above quite fits

· None of these quite match

Tell us what's going on

· Rinse FM / Kool FM are not working for me. Every other radio station I have tried works perfectly (Radio Paradise FLAC, BBC Radio 6 AAC, NTS 1 MP3 etc.). I have tried dozens of radio stations in different formats and the only one’s that don’t work are Rinse FM and Kool FM. When I click play on the Rinse AAC stream it does nothing. I have included a screenshot of the stream that does not work. I am in England, if that helps.

Tell us about your home network

· Roon runs on my PC, that's it. It's not a server or anything complicated.

2

Hmm, both stations work for me in UK.

As you’ve tried other mp3 etc stations, it could be a DNS cache issue. Try rebooting everything.

3

I flushed the DNS cache and Rinse worked temporarily. I tried again a few minutes later, still broken.

4

Strange - it worked for a while and then stopped again? Is that repeatable?

Sounds like an issue with your setup somehow. May be best to open a thread in Support - when you do I’ll add these posts to it.

5

Hello @BrianW,

Thanks for reaching out to Support. Could you please reproduce the problem once more and note the exact timestamp when it happens?

We’ll review the diagnostics report from your machine and look for the cause.

Thanks.

6

Not me, @maezun

7

How do I do that?

8

I reproduced the problem on my machine at 12:52:01 BST

9

Hi @maezun,

Thanks for the report. We’ve taken a look at logs and see a repeating failure wiht this station

The logs actually show the Roon/RAAT stack doing everything right: ICY connect succeeds and the Zone transitions all the way to the buffer. This reflects what you’re seeing in the UI within Roon, and explains why there’s no error listed. But the actual stream then returns no data.

The fact that other users can’t reproduce and a DNS flush temporarily restored playback is a real clue here. admin.stream.rinse.fm is behind a CDN/proxy layer, and you’re likely resolving to a bad edge node.

Try setting your router DNS service to Cloudflare (1.1.1.1) or another known, reliable resolver if you have the ISP presets.

If you’re using a PiHole, try disconnecting it from the network temporarily.

Another note: Rinse FM tends to deliver empty metadata even when the audio stream is correct, so you’ll likely continue to see empty artist/title/album fields in the playbar.

We’ll watch for your reply. Thank you and thanks to @BrianW for investigating.

10

Thanks for getting back to me.

Unfortunately, my ISP does not allow you to change DNS (I am using Virgin Media’s “Hub 4” router).

Is there any other way around it?

To be honest, it’s not the end of the world if I can’t listen to Rinse, I just wanted to know why it wasn’t working, really.

11

I changed to cloudflare dns via my PC network settings. Rinse still does not work.

13

Hello @maezun

We’ve discussed this with our senior QA and development teams. The team is investigating some possibilities here and, as soon as that investigation is complete, we’ll be sure to follow up ASAP.

You have our apologies for the trouble here, and we’ve greatly appreciated your patience as we continue investigating this tricky issue. We’ll be in touch as soon as we can.