Subscribe to alerts

  • 4 Feb 2017
  • 8:32 pm
  • Minor changes and improvements to the control panel

We have made changes to the control panel layout to make the server settings clearer in a more prominent position on the page along with some other small tweaks.

You can also now change your server, this is for cases when the server is hosted far from the broadcast location which can cause skipping and buffering in some cases. Users no longer need to contact support for a server change, simply click the ‘Change’ button next to the ‘Address / Host’ setting and choose a new server from those available.


  • 3 Feb 2017
  • 4:22 pm
  • Server reboot

Due to some issues with the server, we are rebooting it shortly. Please allow 15 minutes or so for your stream to come back online.

We have made improvements to the system so that servers now come back up automatically after a server reboot.


  • 18 Jan 2017
  • 10:34 pm
  • Reboot update

The server has failed to come back online within the usual amount of time after a reboot. An engineer is scheduled to check the server and bring it back online asap.

Apologies for any inconvenience caused and thank you for your patience.


  • 18 Jan 2017
  • 10:23 pm
  • Server reboot

Due to the some issues, we are rebooting s3. Service should be back to normal shortly.


  • 16 Jan 2017
  • 1:21 pm
  • Reboot of S17 server

We are experiencing some slowness on s17 so it will be rebooted shortly.


  • 13 Jan 2017
  • 5:56 pm
  • Statistics Relay for SHOUTcast V2 in SAM Broadcaster

SomeĀ  versions of SAM Broadcaster don’t support statistic relays for Shoutcast V2 servers, however there is a workaround for this.

In the Statistic Relay settings, it will ask for your server address/host, port and password. Enter your address/host and password as normal. The port should then be entered in the following format:

8000/stats?sid=1

Change 8000 to your port number.

Once you’ve added the extra values to your port, the statistics should start working again. If not then use the ‘Force Update’ option a few times until it does.


  • 20 Dec 2016
  • 9:05 am
  • Server Reboot

Due to an issue with the server, we need to reboot it. Apologies for any inconvenience caused.

The server should be back in 5-10 minutes.


  • 20 Dec 2016
  • 9:04 am
  • Server Reboot

The server required a reboot due to an issue that’s causing it to run slow. Apologies for any inconvenience caused.

The server should be back up in 5-10 minutes.


  • 18 Dec 2016
  • 1:18 pm
  • Not able to start your V2 server?

We have had a few users report that they can’t start their V2 server. In almost every case it was due to the ‘stream password’ and ‘admin password’ being the same.

If you have any problems starting your server then please change your admin password to something different.

We will be adding an update in the week to disallow the same password to be entered as the stream and admin passwords.

Update: We have now added a fix to the control panel that updates the admin password if it’s the same as the stream password.


  • 15 Dec 2016
  • 5:18 pm
  • Google Chrome Changes

As of the most recent update of Google Chrome, they have decided to stop supporting the ICY headers that are used by Shoutcast 1.9.

We have made updates to our system to ensure that listeners using Chrome can still listen without any problems using our player. However, if you are an upgraded user and use a alternative Flash/HTML5 player on your website then you may find that some listeners can’t connect to your stream.

You can fix this by either using our web player, or you can change your Shoutcast server to version 2.4 via the user area.

Making your Shoutcast V2 server public

A few extra steps are required to make a V2 server public, this involved setting up an AuthHash. To do this simply:

  1. Log in at myradiostream.com
  2. Scroll down to AuthHash
  3. Click the Manage AuthHash button
  4. Click Create AuthHash – this will log you into your DNAS Admin
  5. Enter your station details and click the Create AuthHash button
  6. Save your changes and this will take you back to the control panel

Server
ID
Current
Status
Mar
Uptime
s1 checking
s2 checking
s3 checking
s4 checking
s5 checking
s6 checking
s7 checking
s8 checking
s9 checking
s10 checking
s11 checking
s12 checking
s13 checking
s14 checking
s15 checking
s16 checking
s17 checking
s18 checking
s19 checking
s20 checking
s21 checking
s22 checking
s23 checking
s24 checking
s25 checking
s26 checking
s27 checking
s28 checking
s29 checking
s30 checking
s31 checking
s32 checking
s33 checking
s34 checking
s35 checking
s36 checking
s37 checking
s38 checking
s39 checking
s40 checking
s41 checking
s42 checking
s43 checking
s44 checking
s45 checking
s46 checking
s47 checking
s48 checking