Radio Riel on Web-based players

in Radio Riel Information

by Elrik Merlin on Wednesday, 4 January, 2017

Due to a security implementation, recent versions of the Chrome and Safari browsers will no longer play our streams using web players including the official StreamLicensing Web player. For the time being you can use Firefox, but they will no doubt implement a similar configuration at some point in the near future.

We’re working on a fix for this, but it is very likely to require us to change all our listening URLs (as a server update is probably required at some point), so we will give you as much warning as we can in advance of any major changes.

In the meantime, if you want to listen to us on the Web with any browser, we suggest that you use the TuneIn curated listening service. This link will search for Radio Riel on the TuneIn service. (It may bring up a few other things too, but mainly us.)

Alternatively you can use an outboard player such as VLC  (all platforms) or TapinRadio (Windows only), both of which will also receive our experimental HE-AAC broadcasts. Either copy and paste the stream URL from the links top left of this page — maybe bookmark them in the player — or tell your browser that you want a player application to handle files of type ‘listen.pls’.

We’ll keep you informed on developments in this area.

Experimental player


{ 2 comments… read them below or add one }

Otenth January 4, 2017 at 19:13

I certainly hope does something about their player quickly. I can vouch for the utility of TuneIn. I use it with my Sonos system and enjoy the variety of ways in which I can browse radio stations (terrestrial and online) in a variety of ways.


Elrik Merlin January 5, 2017 at 01:41

The problem isn't the StreamLicensing player. ANY web-based player in Chrome (55 or later) or Safari will fail. Right now, you can (still) use the StreamLicensing player in Firefox.

Technically this is because both browsers now block non-standard port numbers being referenced in http 0.9 headers - and this is what Shoutcast Version 1 servers use.

The solution is to move either to Shoutcast v2 or Icecast v2, neither of which have this issue. I would prefer Icecast, frankly, but there are a couple of queries regarding royalty accounting that need to be addressed.



Leave a Comment

Previous post:

Next post: