Announcement

Collapse
No announcement yet.

Non-Port 80 Shoutcast Streams unplayable on Chrome 55 and Safari 10

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Non-Port 80 Shoutcast Streams unplayable on Chrome 55 and Safari 10

    Hi Shoutcast Tech team,

    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:

    * Chrome 55 (current beta) - will release 6. Dec 2016!
    * Safari 10 on MacOS Sierra - already released

    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.


    References:
    * https://forums.developer.apple.com/thread/66586
    * https://bugs.webkit.org/show_bug.cgi?id=164530
    Last edited by antonkeren; 28 November 2016, 18:54.

  • #2
    To be more exact, we tested with this version of Chrome: 55.0.2883.59 beta (64-bit)

    Comment


    • #3
      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

      Comment


      • #4
        I updated my Google Chrome to version 55 (x64) and the streams with other ports than 80 on DNAS v2.4.7.xxx and DNAS 2.5.1.xxx can be played without a hit!

        Comment


        • #5
          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.

          Comment


          • #6
            Thought that version in the question was odd, because when you go to your shoutcast page, it clearly states it's running v1.9.8
            "If you don't like DNAS, write your own damn system"

            So I did

            Comment


            • #7
              Can somebody maybe hack Shoutcast 1.9.8 to fix the issue?
              The culprit appears to be the response "ICY 200 OK" instead of the correct HTTP/1.0 string.
              See https://bugs.chromium.org/p/chromium...tail?id=669800

              Another option is to run shoutcast 2.4+ configured in compatibility mode (single stream). This is not very simple to do. Or is it?
              Last edited by meatie; 8 December 2016, 20:03.

              Comment


              • #8
                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.

                Comment


                • #9
                  I had no idea so many people still used SC v1. From the bug report:
                  Originally Posted by internetradio.org.uk on Chromium bug forum
                  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.
                  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.
                  It looks like we all finally have a good reason to upgrade to v2!
                  the detour network - detour MUSIC, detour TALK

                  Purple Zebra Consulting-http://purplezebra.us
                  Supporting independent internet radio stations since 2001!

                  Comment


                  • #10
                    SHOUTcast Server v2.0.0.29/posix(linux x64) also broken on latest Chrome

                    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

                    Are others having this same issue with V2 Shoutcast servers?



                    Thanks in advance for any thoughts!

                    ~ Bill

                    Comment


                    • #11
                      Following up on this, can anyone confirm newer versions of the DNAS do still work with Chrome 55.0? Any advice would be appreciated.

                      Comment


                      • #12
                        Originally Posted by cahaba View Post
                        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

                        Are others having this same issue with V2 Shoutcast servers?



                        Thanks in advance for any thoughts!

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

                        Originally Posted by antonkeren View Post
                        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.
                        the detour network - detour MUSIC, detour TALK

                        Purple Zebra Consulting-http://purplezebra.us
                        Supporting independent internet radio stations since 2001!

                        Comment


                        • #13
                          Upgrade solves the issue

                          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

                          Comment


                          • #14
                            Originally Posted by cahaba View Post
                            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

                            Comment


                            • #15
                              ... you just replaced the sc_serv (v1) with the sc_serv (v2) ??? Conserving the configurations...

                              Can't do that -- v1 config options are not the same as v2. You can only do that from one v2 version to another.

                              edit:4clarity
                              /* v2 HTML5 / Player test pages DigitalMixNYC, DigitalMixNYCbx | DNAS Status: Now Playing js codes (scaststatus_X.php) | PortForward.com | Upload/Download Speed Test | No-IP.com: Free Dynamic DNS | In the YP | dnasDir */

                              Comment

                              Working...
                              X