Latest Chrome browser update (v55) breaks Shoutcast v1.x HTML5 players

More Support

Level 2 Support
Staff member
Apologies for the delay on responding on this. We have indeed already been working on a solution in anticipation for this happening at some point although admittedly we didn't expect it to come so soon and without notification in the original bug report. We've already been trialling https streaming on a few test servers with a few clients who requested it over the past year so rest assured we do have a solution.

Unfortunately there's nothing built into default Centova Cast that can do this but we've managed to tweak some of the config to take advantage of the web proxy and instead of just allowing proxying on port 80 we've extended it to also proxy on port 443 (https / ssl). We've just finished scrambling to update all the server configs to support this and now you can use the following URL structure to get a https stream for your station:

https://server.internet-radio.com/proxy/username?mp=/stream (Swap out the server part for your server (i.e. uk1/uk2/us1...) and the username part for your actual username.)

We've also added a new "quick link" which shows your new "SSL Web Proxy" in your control panel here: https://control.internet-radio.com:2199/client/index.php?page=quicklinks Its probably easier just to go there and get the SSL URL rather than work it out yourself.

We're still working on a fix for the start pages but expect to have it rolled out by the end of the day or tomorrow at the latest. We'll keep you posted on that in this thread.
 

More Support

Level 2 Support
Staff member
We've just modified all the start pages to use the new https / "SSL Web Proxy" links. Our preliminary testing shows all Shoutcast 1 / 2 and Icecast 2 stations to be playing as before. Let us know in the thread below or via our contact form if you notice any issues.
 

realdanceradio

New Member
Sadly mine is still not working, both in Chrome and Firefox! Still displaying the "no web player"

I've cleared cache on my Chrome browser, have I missed something?
 

More Support

Level 2 Support
Staff member

MoveDaHouse

New Member
only way is to turn allow insecure content on within the browser for their site, they will need to do something for those with http streams, maybe allowing to submit a https stream url update via a contact form or that directory is gonna only just play https streams in the future & lose alot of traffic, ive currently been updating alot of my listings with the new https proxy stream, tunein etc & about 20 others & all have been updated & working now, what a pain... is there not a new update for the shoutcast DNS? says here there is 2.6 now http://forums.winamp.com/showthread.php?t=453775 currrently on SHOUTcast Server v2.5.5.733
 

More Support

Level 2 Support
Staff member
only way is to turn allow insecure content on within the browser for their site, they will need to do something for those with http streams, maybe allowing to submit a https stream url update via a contact form or that directory is gonna only just play https streams in the future & lose alot of traffic, ive currently been updating alot of my listings with the new https proxy stream, tunein etc & about 20 others & all have been updated & working now, what a pain... is there not a new update for the shoutcast DNS? says here there is 2.6 now http://forums.winamp.com/showthread.php?t=453775 currrently on SHOUTcast Server v2.5.5.733
They do run a non-secure version of their site (without a redirect) which still works fine (http://directory.shoutcast.com/) so perhaps people will start using that instead. As there's no login or forms to send data on their directory site they could just redirect all the https traffic to the non-https version and that would solve the problem.

Shoutcast v2.6 has been out for a while now but they started limiting the maximum bandwidth to 128 kbps unless you pay them $9.90 per month for their premium service. We have plenty of Shoutcast 2 users that broadcast higher than 128 kbps which is one of the reasons we've refrained from upgrading for the time being.
 
Top