PureStream (Whisperings Solo Piano Radio) custom stream URL works in browser but fails in Roon Live Radio

Hi,

I am a PureStream subscriber of Whisperings: Solo Piano Radio and I am trying to use my personal PureStream stream URL with Roon Live Radio.

Whisperings support provided the following non-secure stream URL specifically for use with Roon (they said Roon cannot use the https version):

http://live.str3am.com:3120/secure2?username=***&password=***

When I open this URL in a browser on my Roon Core machine, the stream plays fine. So the URL itself and my network connectivity (including port 3120) are working correctly.

However, when I add this URL as a custom Live Radio station in Roon, Roon tries to play it but quickly stops with the message:

“Playback was interrupted because a track failed to load”

I have also tried adding other Whisperings URLs (like the free stream) and they either do not play or behave similarly, while other Live Radio stations and Qobuz/Tidal in Roon work without any issues.

Whisperings told me that this URL format has worked for other Roon users in the past, so I would be grateful if you could check whether there is any limitation or bug in Roon’s Live Radio handling for this type of authenticated HTTP stream (username/password as query parameters on port 3120).

If helpful, I can provide logs from my Core right after trying to play this station.

My setup:

  • Roon Core: [OS / device]
  • Roon version: [version number]
  • Output zone(s) tested: [e.g. RAAT endpoint, System Output]
  • Network: [e.g. wired / wireless]

Thanks a lot in advance for your help.

Best regards,
Best, Christian

Hello @Christian_Fingerhut , I can play Whisperings: Solo Piano Radio from the Roon database without problems .

You say you can’t play the free stream - that should be the same as Roon’s:

https://pianosolo.streamguys1.com/live
(or
http://pianosolo.streamguys.net/live)

If you can’t then there is something wrong with your system.

If it’s a different URL then can you post it and I’ll check it.

In general Roon has no difficulty with query parameters on streams with port numbers (it does sometimes have difficulty on such https streams but that’s not the case here). Such personal URLs have been used in Roon before.

If there is indeed something wrong with the personal URL on Roon then if you wish you could PM me the URL and I’ll check it on my system and look at the logs.

Purestream (the paid subscription) not the free stream…

You also said you couldn’t play the free stream - and that was something I could check.

This almost certainly should be:

https://live.str3am.com:3120/secure2?username=***&password=***

So, “https” instead of “http”.

That server does not provide an https stream.

That may be, but it does appear to have a mostly valid TLS cert:

Reference: SSL Checker

I don’t have an account, so I don’t have a way to test beyond that. These days, it’s uncommon for services to support reusable passwords without encryption.

That’s interesting. I see that same result but if I try and connect I get
net::ERR_CERT_COMMON_NAME_INVALID

(Presumably the name mismatch error)

Nevertheless, the http connection works. So something else is causing Roon problems.

Yes. That is odd. This URL has no cert errors, but I don’t know if it provides the same content:

https://live.streamguys1.com:3120/

It seems to:

Mount Point /secure2                      Login

Stream Title:Whisperings PureStream: Solo Piano Radio
Stream Description:Music to Quiet Your World
Content Type:audio/mpeg
Mount Start:28/May/2026:11:31:06 -0500
Bitrate:128
Current Listeners:5
Peak Listeners:7
Stream Genre:Classical
Stream URL:http://www.solopianoradio.com
Current Song:Wordless Flight - A Good Life for Ellis & Adaline/Wedding in a Week

@Christian_Fingerhut , can you try using
https://live.streamguys1.com:3120/secure2?username=***&password=

Try https first, if that fails (remember Roon sometimes has problems with https and port numbers), then try http.

unf. still roon cannot find it…

Did you try the http form rather than https?

I think the logs need to be looked at.
If you open a thread in Support the Roon support staff can look at the logs and determine what is going wrong.