Shoutcast DNAS 2.6 (Build 753) 23 Jul 2019

[DJ Egg]

This release is now available for the following platforms:

• Windows 32-bit (Windows 2000 and up)
• Windows 64-bit (Windows XP64 and up)
• Linux
• Linux 64-bit

This release is currently not available for the following platforms:

• BSD (8.x)
• Raspbian (Raspberry Pi - works on RPi A/A+/B/B+ and RPi2 with the same compile!)
• Mac OS X (Intel)

We hope to have builds for Mac, BSD & RasPi available ASAP.
For now, you will need to keep using v2.4.7 instead. Sorry.


Downloads

Download links can be found under Profile => Your Plan in the new RMO.

Premium subscribers will also find unlock codes & instructions there.


Changes

• Premium 2.6 features:
• Native SSL stream support (https)
• Personal & Customisable SSL Certificate
• Improved scalability (support up to 12k listeners)
• Improved backup stream url support
• New authhash system for 2.6 and higher only
• Premium radiomanager control panel support
• Improved monetization features and trigger methods
• General bug fixes (free and premium versions)

Getting Started

If you already have a running instance of the 2.x DNAS then there should not be any issues with replacing your current version with this new version.

Refer to this tutorial for upgrade instructions
http://help.winamp.com/customer/en/p...ading-the-dnas

If this is a new install then make sure to read through the information in 'Readme_DNAS_Server.html' and the related documentation as well as considering using the setup mode which should make it easier to get started over all prior 2.x builds (and 1.x based releases).

Finally, all current copies of the documentation are included with the installer / archive and is the recommended point of reference for this release. The information found online at http://wiki.shoutcast.com/wiki/SHOUTcast_Broadcaster for the DNAS server might still be out-of-date in places....

For those who do not wish to upgrade, DNAS v2.4.7 and v2.5.x streams are still listed in the Shoutcast Directory and are not restricted by Freemium vs Premium mode like v2.6


SSL Certificate Support

[Premium feature only]

Add to sc_serv.conf

sslCertificateFile=ssl.crt
sslCertificateKeyFile=key.pem/.key

(obviously needs to refer to the correct filenames)

Put the whole certificate chain in the .crt file, and only the key in the .key file.


Reporting Issues

If you do come across an issue with the DNAS, then please post in this thread with as much information as possible about what you're doing at the time, the system you are using and anything else which will make it easier to understand what is or isn't going on with your install.

Posts relating to authhash management issues will be ignored as this is not the thread for posting such issues. The correct thread is here.

However, where sensitive information is concerned, we recommend that use the support/help system instead: https://help.shoutcast.com


Known Issues

Watch this space!

______________________________________________________________________________________


Discussion about previous versions of the server including changelogs can be found in the following threads

• GM (Build 733)
• GM (Build 724)
• GM (Build 256)
• GM (Build 167 / 168)
• GM (Build 164 / 165)
• GM (Build 147)
• GM (Build 123)
• GM (Build 109)
• GM (Build 107)
• GM (Build 29)
• RC2 (Build 28)
• RC (Build 27)
• Beta (Build 18 + 19)
• Beta (Build 17)
• Beta (Build 13 + 14)
• Beta (Build 10)
• Beta (Build 7)

[Klaas]

I can now connect the aacp stream again and there is no message about invalid authhashes. However the DNAS doesn't seem to be downloading any ads and playing them when the trigger is played. In the past the server would log when ads are downloaded from the server and when the trigger is played.

Using on x64 linux.
(ISN Radio)

[AnthologyWeb]

Hello, yes i confirm no ads are played with that version.

[Klaas]

I've created a support request however didn't get a response yet for that issue.

[AnthologyWeb]

So did I.
I think they're working on it.

[Klaas]

Hopefully. I asked if it makes sense to remove the ad trigger for now or if there will be a solution very soon. No response yet.

[AnthologyWeb]

For now i'm still on 2.5 version

[DJ Egg]

Build 748 is now available
which is supposed to fix reported monetization issues.....

[Klaas]

With the newest build I'm just getting a "response returned 500, NOK" from YP.

[DJ Egg]

Build 750 is now available

- ssl is reported to YP
- pause, flex and fixed ad breaks are supported
- other minor fixes and tweaks

[brando1962]

I Try the new build 750.

Till the published IP is the main server IP and not IP binded in the configuration file, and till the new directory publish all mountpoints in the same link (with differents formats in the same link)... the 2.6 is impossible to use in production.
All things that in the previous 2.5 (and the old YP system) worked fine.

And we are paying for a server that is not possible to use at the moment.
(or use only for a joke station, with a poor simple server and only 1 mountpoint)
All great streaming providers use to Bind a failover IP in the server. The best way to move the service to another server in fast way without change the streaming IP (in case of fail of the machine).

[BDorin]

This version Shoutcast DNAS 2.6 (Build 750) crash my autoDJ script SC_TRANS, i use a previous version SHOUTcast Server v2.5.5.733 and its working great.

[stoicite]

It would be great if I could login to radiomanager.shoutcast.com .. but even though I have a valid account, it won't let me login, only gives a bad username/password error.

[outpostradio]

2019-01-19 12:47:37 INFO *********************<<RUNNING_IN__DAEMON_MODE>>*********************
2019-01-19 12:47:37 INFO ** SHOUTcast Distributed Network Audio Server (DNAS) **
2019-01-19 12:47:37 INFO ** Copyright (C) 2014-2019 Radionomy SA, All Rights Reserved **
2019-01-19 12:47:37 INFO *********************************************************************
2019-01-19 12:47:37 INFO [MAIN] SHOUTcast DNAS/posix(linux x64) v2.6.0.750 (Dec 7 2018)

2019-01-19 12:57:46 INFO [SRC 127.0.0.1:43650 sid=1] SHOUTcast 1 source connection starting.
2019-01-19 12:57:46 WARN Trouble parsing intro
2019-01-19 12:57:46 WARN [SRC 127.0.0.1:43650 sid=1] Skipped intro file `/usr/local/shoutcast/mp3/Preroll_57ChevyLoveSongs.mp3' as it is incompatible with the current stream format. Expected 128 kbps, got unknown kbps. Expected unknown kHz, got unknown kHz.
2019-01-19 12:57:46 WARN Trouble parsing backup
2019-01-19 12:57:46 WARN [SRC 127.0.0.1:43650 sid=1] Skipped backup file `/usr/local/shoutcast/mp3/chevyls-fail.mp3' as it is incompatible with the current stream format. Expected 128 kbps, got 1765015555 kbps. Expected unknown kHz, got unknown kHz.

Indeed, listeners do not get the preroll when starting the stream.

The same configuration and files work fine in V733.

[Fiesi]

SSL only Premium?

Personal & Customisable SSL Certificate is on the Shoutcast Server
Software Freemium.

Can i take my cert files from the Domain (letsencrypt?)

[peter2008]

I asked vía ticket about the difference about that few weeks ago, and I don't have answer. I tried to configure a Letsencrypt certificate, and I'm able to load status page via https, but can't listen the station...

[stereoscenic]

I use "stunnel" and letsencrypt to get SSL working... it's sort of strange but it works fine.

code:
sudo apt install stunnel

sudo nano /etc/stunnel/stunnel.conf



[shoutcast]

accept=443

connect=80

cert = /etc/letsencrypt/live/radio.example.com/fullchain.pem

key = /etc/letsencrypt/live/radio.example.com/privkey.pem



sudo stunnel

[vetesgrl]

Still waiting for FreeBSD binary

[DJ Egg]

Build 753 now available

Fixes:
Authhash YP registration issues
Premium Licence registration issues
Various monetization related issues
Stream URL in RMO always showing as https:// instead of just http://

Timestamps on the builds are April & May.
Public release required various serverside fixes first (database, YP, APIs, RadioManager)


Downloads can be found via the Manage Your Plan link in the RadioManager.

[peter2008]

Has anyone managed to configure the service by https (with your own certificate? As in the previous version, to load the status page via https works fine, but the rest, error ... (The Personal & Customisable SSL Certificate of the free version)

[ilhan]

I receive below Warning constantly:

[YP sid=1] response returned 500, NOK

How can I register to Directory successfully?

[LStratmann]

Hey,
This is because the server cannot connect to the YP.
This is unfortunately the case in the meantime and cannot be prevented.

Greetings.

[LapTop]

edit my fault, it work

[LStratmann]

Hey,
Do you use Linux or Windows?

[jbmusic]

Is there anyone wo can help me to config the dnas server. We have the premium account, but this is not working for us. AS a local broadcaster we have to serve the city and for the moment we are facing this issue and the support we got from SC is poor

[LStratmann]

Open a new topic and ask the question e.g. describe your error message. We will then try to help you.

[jbmusic]

I just did... i hope somebody could help us sorting this out!

[djSpinnerCee]

what? is "not working" for you?

[jbmusic]

I have tried several certificates without any succes. Now i have made a new free SSL certificate by https://zerossl.com/ and now i get the warming

WARN [MAIN] Invalid private key file C:\Program Files\Shoutcast\ssl\privat.key
2020-03-24 22:17:14 WARN [MAIN] failed to set up SSL, key values mismatch

[jbmusic]

the certificate is not trusted in all web browsers. You may need to install an Intermediate/chain certificate to link it to a trusted root certificate. Learn more about this error. The fastest way to fix this problem is to contact your SSL provider.

we are working on Windows server 2016

[jbmusic]

a small update;
the SSL certificate is working.
when i do a test on the Destip included port 8444 it respondes that the certificate is okay.

now the issue why shoutcast is not responding.
it stil remains on:detected ssl request, checking further

a part of the config file:

sslcertificatefile=C:\Program Files\Shoutcast\ssl\stream.crt
sslcertificatekeyfile=C:\Program Files\Shoutcast\ssl\privat.key
destip=stream.lokaleomroepzeewolde.nl
publicip=stream.lokaleomroepzeewolde.nl
PublicServer=always
alternateports=8444

details:
Windows Server 2016
Shoutcast Server v2.6.0.753/win64
premium account
connected shoutcast true Proppfrexx

the

[DJ Egg]

Afaik, the path should be relative to sc_serv, so if sc_serv is installed in C:\Program Files\Shoutcast (not recommended, unless the folder's been given Write permissions), then the ssl cert path would be just =ssl/stream.crt

Is =ssl/privat.key a typo? (i.e. should it be =private.key)


Other than that, I see http://stream.lokaleomroepzeewolde.nl:8444 works ok, but https://stream.lokaleomroepzeewolde.nl:8444 does not :-(

Secure Connection Failed
An error occurred during a connection to stream.lokaleomroepzeewolde.nl:8444. PR_END_OF_FILE_ERROR

[jbmusic]

DJ Egg,

thanks for your reply.
i changed the path... ssl/privat.key
and nope it's not a typo...

the normal http stream is working properly but when i use the https i get the error...

What could i do to solve this issue there we are a local public broadcaster to inform all the citizens

[LStratmann]

Why not use the normal https port 443?

[jbmusic]

Hi...
the normal 443 port is already in use for some other purpose...

just put on all the debug info i could enable;

020-03-25 13:47:28 DEBUG detected ssl request, checking further
2020-03-25 13:47:28 ERROR [RECV 77.170.230.60:57768] Socket error while waiting for data. err=error code 0(0)
2020-03-25 13:47:28 DEBUG [THREADRUNNER] Removing microConnection [done: 0, exception: 1]
2020-03-25 13:47:28 DEBUG [THREADRUNNER] Removing microConnection from thread 2
2020-03-25 13:47:28 DEBUG detected ssl request, checking further
2020-03-25 13:47:28 ERROR [RECV 77.170.230.60:57769] Socket error while waiting for data. err=error code 0(0)
2020-03-25 13:47:28 DEBUG [THREADRUNNER] Removing microConnection [done: 0, exception: 1]
2020-03-25 13:47:28 DEBUG [THREADRUNNER] Removing microConnection from thread 2

[LStratmann]

Back when I was using SSL, everything was going perfectly. It's weird.
You also entered the license key and the UID? Because if the SSL certificate was wrong, there would be a HTTPS error on the browser side.

[jbmusic]

Yes, we did as well...
licenceid=XXXXXX
userid=XXXXXXXX

i have already made a test-environment so i can tweak etc. but also the same issue.
could there be something wrong on the side of shoutcast-server?
When i visit the shoutcast dashboard i see listed on their website the players and they all are with https.... but they are not working..

[DannyGHE]

Hi jbmusic,

I have exactly the same problem also with an installation on Windows.

I have successfully tested the SSL reponse with https://www.sslshopper.com/ssl-checker.html which means that the certificate is correct.

Nevertheless , Shoutcast is not working ( responding) in https on Windows ... why ?

[LStratmann]

As far as I know there are no problems with Linux.

[jbmusic]

Our station is on windows and no linux...