I'm Anton - Website Product Manager from radio.net - and would like to inform you that Shoutcast streams below DNAS v.2.5. running on ports other than 80 are NOT PLAYABLE on the following browsers based on our research today:

The Streams are blocked by the browser with the following messages:
* Sandboxing 'http://85.214.51.134:36889/;5839676704576158stream.nsv' because it is using HTTP/0.9.
* Cancelled resource load from 'http://85.214.51.134:36889/;5839676704576158stream.nsv' because it is using HTTP/0.9 and the document was loaded with a different HTTP version.
* Failed to load resource: net::ERR_INVALID_HTTP_RESPONSE

As most Shoutcast streams are served via non Port 80 Ports, this issue will be WIDESPREAD. I suggest you get in touch the Google Chrome team to figure out a solution.
Maybe you can provide a patch for server-operators just in time?

We at radio.net are very concerned about this issue as we know many Shoutcast Streams run on ports other than 80. We hope you (or the Browser makers) can alleviate this issue as many station operators (and radio-listeners) will potentially be affected.

Update:
* We have tested 2 streams published with DNAS v2.5.6 and they were also not playable with the current Chrome 55 beta. So it appears that those are also affected.
* We have furthermore reported the issue to the Chromium Team. They at least give some technical hint to resolve the issue on the server side. See: https://bugs.chromium.org/p/chromium...l?id=669800#c6
* Unfortunately the Chromium team is reluctant to revert the changes that prevent playback of many Shoutcast streams on non-standard Ports

Information from a Shoutcast Customer Support Representative:
* v2.5.6 is an old unsupported hacked version from 12 years ago. (that would explain my test results)
* Official builds of DNAS v2.4 and newer should not be affected.

1.9.8 is not supported since more than 10 years. With v2.x is it the same as know it from 1.9.8. You have to modify/change only some parameters in the config file to close out outdated params/values. Its really easy to switch to 2.x! Check the docs-folder in the download-package. There you can find all that you need.

Our DB of 91,218 radio servers show that 60,384 are still running Shoutcast v1. This is the vast majority of radio servers that will have any HTML5 players stop working from now o

It also looks like folks are now trying to hack sc v1 to change the ICY response.

Quote:

Originally Posted by jordanmilne.com on Chromium bug forum

I patched DNAS version 1.9.8 to send radio streams back with an "HTTP/1.0" response line instead of "ICY": <website removed> .

I'm not familiar enough with SHOUTCast clients to know if that's kosher or not, but it seems to unbreak playing in Chrome 55 and might be an OK stopgap between DNAS 1.9.8 and 2.x. The protocols seem to have the exact same semantics.

This thread appears to suggest that Shoutcast V1 servers are suffering from the non-standard port HTML5 issue, but my SHOUTcast Server v2.0.0.29/posix(linux x64) is also unplayable with HTML5 on Chrome Version 55.0.2883.87 m

This thread appears to suggest that Shoutcast V1 servers are suffering from the non-standard port HTML5 issue, but my SHOUTcast Server v2.0.0.29/posix(linux x64) is also unplayable with HTML5 on Chrome Version 55.0.2883.87 m

You're running an older version of SC v2. Please see post below. Once you upgrade, you should be OK.

Quote:

Originally Posted by antonkeren

Information from a Shoutcast Customer Support Representative:
* v2.5.6 is an old unsupported hacked version from 12 years ago. (that would explain my test results)
* Official builds of DNAS v2.4 and newer should not be affected.

Just a quick followup to confirm that a Shoutcast DNAS upgrade (to SHOUTcast Server v2.5.1.723/posix(linux x64)) solved my non-standard port issues and HTML5 player problems on Chrome v55. Also, during the unpacking, the existing config file is preserved so the upgrade is easy as pie. Stop the PID, restart the Shoutcast server, and voila! You'll notice some enhancements with the web interface as well, including a player there to facilitate monitoring. Anyone need any help let me know.

Just a quick followup to confirm that a Shoutcast DNAS upgrade (to SHOUTcast Server v2.5.1.723/posix(linux x64)) solved my non-standard port issues and HTML5 player problems on Chrome v55. Also, during the unpacking, the existing config file is preserved so the upgrade is easy as pie. Stop the PID, restart the Shoutcast server, and voila! You'll notice some enhancements with the web interface as well, including a player there to facilitate monitoring. Anyone need any help let me know.

Peace -- Bill

Hello Bill,

I did not try, you just replaced the sc_serv (v1) with the sc_serv (v2) ??? Conserving the configurations?

Hopefully you can help us all easily migrate from shoutcast 1 to shoutcast 2

netyco -- ok, you can, but if you want to be listed, you'll need to add the authhash (but it is added via admin.cgi), and you'll also have to add the adminpasswd, and streampasswd, etc.... yeah, it'll start with a v1 config, and it's a good starting point, but the v2 won't be fully operational without the v2 options you need to change from their defaults.

the v2 dnas needs far less options changed from their defaults to work than the v1 (my config for 2 streams has about 8 lines), so using a v1 config may be overkill on a v2.