Search results

Checking back in today we've noticed packet loss seems to be much better for clients who may have been affected. Were seeing 0% so far today which is perfect.

Hi Chris. Thanks for all these reports and apologies once again. We're working with the network providers now to solve the problem. The problem isn't your end. It appears that migrating us2 to fix the reboot issue has introduced some networking issues for a few clients. In the meantime we can...

Great :) We haven't had any problems with loss of networking since the migration so fingers crossed I think we're back to normal now. That's a relief! I'm sorry to hear that our packages don't suit your station's needs so well. We have tried a variety of different packages and billing methods...

We remember very well the issues of 2016. Our network provider was being DDOSed and have since invested heavily in improved network infrastructure to mitigate those issues and provide much better networking moving forward hence our near perfect uptime during 2017. We feel your frustrations, we...

We're sorry about the recent issues affecting a your server. We have had a tough time dealing with the recent Spectre / Meltdown vulnerabilities. Unfortunately the patches that were applied by our datacenter introduced a bug which would randomly cause loss of networking on a few of our servers...

Apologies for the problem you should be able to access your server now. us2 has had some odd networking issues last night. We're digging into what happened and filing a report with the data centre now.

Hi Luna, Apologies we thought this issue was resolved. There's no "hacking" involved here but I'll explain a little more why you think you're seeing 3 or 4 times the listeners. Some stations load balance their listeners over several servers so we add these together to give a total rather than...

Hi Luna. Thanks for pointing that out. We've identified a bug causing your station to be read twice. Your station should be reporting correctly now.

Thanks chrislong. We've got your email and you'll get a reply shortly.

Hi Chris, We're sorry to hear your having issues. We're not seeing any network issues from our monitoring locations. Can you provide an MTR report as shown here: https://www.internet-radio.com/community/threads/how-to-use-the-mtr-tool-to-analyse-network-problems.535/ An MTR report is more...

Yes, Apologies for the issue there were some connectivity issues late last night. These we're resolved quickly and you shouldn't have any issues today. According to our provider "We have confirmed that the issue is the result of a fiber cut in our upstream provider's network. We are working with...

Hi Lionpaw, The 33 is the amount of people who tuned in during that time period and not necessarily at the same time. The 13 shoutcast DNAs "peak" listeners are the amount of listeners tuned in at the same time. Hopefully this helps clear up the confusion. This is not an error.

We have only foreced https to www.internet-radio.com so basically the forum and directory. The hosting servers (us*/uk*.internet-radio.com) are unchanged so your issue must be related to something else. If you contact support here we can help. No, fortunately :) All old links redirect...

We previously allowed unsecured (plain http) connections to the server but as of today we are redirecting all unsecured connections to the secure (https) version. There shouldn't be any real noticeable difference but please do let us know if you have any problems.

Good News! It appears the Chrome team has decided to roll back the change: https://bugs.chromium.org/p/chromium/issues/detail?id=669800#c103 We still recommend upgrading to ShoutCast 2 though as shoutcast.com will likely remove version 1 stations at some point. We're not sure on the status of...

We're sending the following email out to our remaining customers who are still running Shoutcast version 1: In addition we are enabling a button in the control panels to request the upgrade.

Troubleshooting: Not being listed? Double check your settings and ensure you have followed the above guide. If you're sure everything is correct enable debug logging in your config file by setting loglevel to 4: <logging> <accesslog>access.log</accesslog>...

Hi Hans You don't appear to host with us so I'm afraid we can't help. You'll have to contact your hosting provider.

As we suspected, the Chrome team has marked the issue as "wontfix" meaning they aren't going to revert the changes or fix the issue in the future: https://bugs.chromium.org/p/chromium/issues/detail?id=669800#c68 We have already upgraded some users from Shoutcast v1 and we recommend any others...

We've stopped offering Shoutcast v1 to new users as of now.