View Single Post
Old 25th June 2020, 02:31   #3
Junior Member
Join Date: Jul 2009
Posts: 4
Originally Posted by aaronsnet View Post
I just discovered Stunnel and using it with Shoutcast for https (SSL) streaming without having to have a Shoutcast for Business (Premium) account. Basically, Stunnel takes the Shoutcast server and makes it https (SSL) without having to make any changes to the Shoutcast DNAS config itself. It turned out to be a lot easier than I thought it would be. The biggest hurdle I faced was finding up to date directions. This was done on a dedicated server with: CentOS 6. Also, Shoutcast DNAS and Stunnel were already installed and the port I used for https (SSL) streaming was already open and NOT used by another service.

1. Login to the server as root using SSH.

2. Follow the instructions to create a Let's Encrypt SSH key for Stunnel to use (even if you don't have a Shoutcast for Business account). When I did this, I had several dependencies that needed to be installed before I could actually run the certbot-auto command:

3. Go to the Stunnel directory (cd /etc/stunnel/)

4. Create stunnel.conf file (nano stunnel.conf). Add the following lines and save (CTRL - X):
accept=port that https (SSL) stream should go out on
connect=current domain and port of where your current Shoutcast server is (mine is on the same server which is why I use localhost
cert and key=replace your domain name used in step #2


cert = /etc/letsencrypt/live/
key = /etc/letsencrypt/live/

5. Start Stunnel (/usr/bin/stunnel)

6. Go to<port used for Stunnel> and you should see your Shoutcast v2 page if everything worked correctly.

(PS: I hope that the Shoutcast admins will not remove this post post, especially for us with very limited budgets trying to reach the largest audience possible.)
can you post the sc_serv.conf please?
i do all the steps and shoutcast say can't bind on 443 port...
please help!
TiaNcl is offline   Reply With Quote