- 14 Apr 2017
- 1:21 pm
- Service restored
Service has now been restored. Thank you for your patience and apologies for any inconvenience caused.
Service has now been restored. Thank you for your patience and apologies for any inconvenience caused.
Earlier this morning, the server s16 froze and some tests were performed as a result. We have identified a hard drive issue which is the cause of the problems.
The server is being booted back up now, it will hopefully come back online but we are also going to schedule a hard drive replacement as a permanent fix.
If you need to get your stream back online urgently then you can change to a different server by clicking the ‘Change’ button next to the server address. Please note that this will allocate new server settings.
Due to faulty hardware, the server S30 is due to be replaced in the next 2 days or so. This will mean a change of IP address.
The change won’t affect the majority of customers, but if you do stream using the IP Address (198.255.100.162) rather than the Hostname (s30.myradiostream.com) then you will need to update your settings.
Once we have the new IP, an update will be posted here.
We have had some issues with the s30 server and are planning a reinstall. This will be started in 1 hour from the time of this post.
If you are hosted on s30 you will notice up to an hour of downtime (although it should be more like 20 minutes). This should stop the server resets that have been happening regularly.
Thank you for your understanding and apologies for the inconvenience caused.
Update: Unfortunately as this server is hosted in a facility that doesn’t support remote OS reinstall, the planned reinstall is being cancelled for now. Updates will follow in the coming days.
Late last year, Google Chrome made technical changes that effectively stopped Chrome users from being able to listen to Shoutcast V1 streams.
It has been brought to our attention that Chrome now supports V1 again so web players will work in all browsers as they did previously.
We have now updated all Shoutcast V2 servers to the latest version (2.5.1).
Please restart your server to complete the upgrade if you use V2 mode.
Some customers may see the following message on their server if using V2:
“Please login or see here to find out more about the new DNAS version.
Please install this update as soon as possible, thank you.”
We will be applying updates next week, please don’t open a support ticket regarding this – the update will be rolled out to all customers from Monday.
Due to the server becoming unresponsive, it has been rebooted. Streams should come back online in 15-20 minutes.
Apologies for any inconvenience caused.
Since more users have been updating to Shoutcast V2, we have had rare occurrences of servers freezing and causing the control panel to ‘hang’ when logging in. Restarting the server didn’t always work as the frozen process couldn’t be stopped.
A new feature has been introduced from today that will detect on login when a server is loading very slowly or frozen and give the option to force a hard restart – this will stop the frozen process and restart your server, eliminating the need to open a support ticket and wait for the issue to be resolved manually.
A fault was detected by our automatic monitoring system at 15:24 and after investigation we have found that the hard disk has failed.
The disk will be replaced as soon as possible, this may take several hours.
If you are affected then your server will come back up automatically when the work is complete.
If you can’t wait until the server is fixed then you can change to a different server. Please note that this will issue you with a new address and port and you will need to reconfigure your streaming software as well as any links or listings on directories such as tunein. We recommend waiting for the server to come back online, changing your server should be a last resort.
Apologies for any inconvenience caused.
UPDATE: Having reinstalled the server, it is now working as normal and hard disk replacement has been cancelled.
| 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 |