How to Install SHOUTCast Radio Server (Online Media Streaming) on Linux

SHOUTcast is proprietary software used to stream media over the Internet, especially used in music live streaming by the radio stations on Internet, and is developed by Nullsoft with versions for all major platforms, including Linux.

This tutorial will guide you on how you can install The SHOUTcast Distributed Network Audio Server in CentOS 8, with the help of which you can use media players, like Winamp or Mixxx to connect to the streaming services and broadcast your audio playlists to Internet listeners.

Although this tutorial only covers SHOUTcast server installation on a CentOS 8/7 machine, the same procedure can be applied to other Linux distributions such as RHEL, Fedora, Ubuntu, Debian, Linux Mint, etc. with the remark that you must adapt firewall commands to suit your Linux distribution.

Step 1: Download and Install SHOUTcast Server

1. Before proceeding with the installation of the SHOUTcast server, create a local user from which you will run the server because running the server from the root account can impose serious security issues on your system.

So, log in on your system with the root account, create a new user, called radio, after you’re done log out from the root account, and, then, login with your newly created user. Here are the following required commands that need to be executed on the terminal.

# adduser radio
# passwd radio
# su - radio
$ pwd 
Create New User in Linux
Create New User in Linux

2. Once logged in on your system with the radio account, create two directories named download and server, then switch to download folder.

$ mkdir download
$ mkdir server
# cd download

3. Next, grab the last version of the SHOUTcast server archive for Linux, depending on your system architecture, by visiting the official Nullsot Download page.

  1. http://download.nullsoft.com/shoutcast/tools

Alternatively, use the following wget utility to download the archive from the command line.

--------------- On 64-bit ---------------
$ wget http://download.nullsoft.com/shoutcast/tools/sc_serv2_linux_x64-latest.tar.gz

--------------- On 32-bit --------------- 
$ wget http://download.nullsoft.com/shoutcast/tools/sc_serv2_linux-latest.tar.gz
Download Shoutcast Server
Download Shoutcast Server

4. After the download completes, extract the archive file, list the directory to locate the sc_serv executable binary file, and copy it to the installation directory, located in the server folder, then move to the SHOUTcast installation path, by issuing the following commands.

$ tar xfz sc_serv2_linux_x64-latest.tar.gz
$ ls
$ cp  sc_serv  ../server/
$ cd  ../server/
$ ls
Extract Shoutcast Archive
Extract Shoutcast Archive

5. Now that you are located in the server installation path, create two directories named control and logs and you’re done with the actual installation process. List your directory content to verify if everything is in place using ls command.

$ mkdir control
$ mkdir logs
$ ls
Confirm Shoutcast Files
Confirm Shoutcast Files

Step 2: Create a SHOUTcast Configuration File

6. In order to run and operate the server, you need to create a configuration file for SHOUTcast. Open your favorite text editor and create a new file, named sc_serv.conf.

Make sure that this file is created in the same path as your sc_serv e executable binary files are created. Using pwd command should show you this absolute path – /home/radio/server).

$ cd /home/radio/server/
$ pwd
$ vi sc_serv.conf
Create Shoutcast Configuration File
Create Shoutcast Configuration File

Add the following statements to sc_serv.conf file (example configuration).

adminpassword=password
password=password1
requirestreamconfigs=1
streamadminpassword_1=password2
streamid_1=1
streampassword_1=password3
streampath_1=http://radio-server.lan:8000
logfile=logs/sc_serv.log
w3clog=logs/sc_w3c.log
banfile=control/sc_serv.ban
ripfile=control/sc_serv.rip

Some important settings that you should be aware of this file are password statements, which you must be changed accordingly:

  • adminpassword – Admin password required to perform remote administration via the web interface to the server.
  • streampassword_1 – Password required by the remote media player to connect and stream media content to the server.

Alternatively, if you want to create a configuration file for the SHOUTcast server you can go to download directory and run builder.sh or setup.sh scripts.

$ cd ../download/
$ bash setup.sh

which will let you configure the server from a web interface that can be accessed from the following address.

http://localhost:8000
OR
http://ipaddress:8000
Shoutcast DNAS Setup
Shoutcast DNAS Setup

Once the configuration is created you can copy it to the server installation directory.

7. To start the server execute sc_serv the file from your current working directory, which must be the server directory, put it on background with & bash operator, and direct your browser to http://localhost-or-IP:8000 URL.

Also, use netstat command to see if the server is running and on what port numbers it listens.

$ chmod +x sc_serv
$ ./sc_serv &
$ netstat -tulpn | grep sc_serv
Check Shoutcast Server Ports
Check Shoutcast Server Ports

Step 3: Open Firewall Connections

8. Now the SHOUTcast server is up and running but it can’t be accessed yet from the outside world due to CentOS Firewall restrictions. To open the server to external connections login with root account and add the rule that will open port 8000 TCP.

After the rule has been added reload the Firewall to apply changes and logout from your root account.

$ su -
# firewall-cmd --add-port=8000/tcp --permanent
# firewall-cmd --reload
# exit

9. Then open a browser from a remote machine and type your server IP Address on port 8000 on URL filed – http://192.168.1.80:8000 – and the SHOUTcast web interface should appear like in the screenshot below, with no live streams available.

Shoutcast Server Summary
Shoutcast Server Summary

Step 4: Manage SHOUTcast Server and Create Daemon script

10. The command used to manage the SHOUTcast radio server is the binary file itself, which must be run from its installation path location in order to be
able to read the configuration file. To run the server as a daemon using the daemon command option.

You can also instruct the server to read its configurations from a different location by indicating where the configuration file resides, but be advised that using this option requires the creation of logs and control directories, which can be confusing in practice and can lead to server inability to start.

$ pwd  ## Assure that you are in the right installation directory - /home/radio/server

$ ./sc_serv   ## Start the server in foreground – Hit Ctrl + c to stop

$ ./sc_serv daemon  ## Start the server as a daemon

$ ps aux | grep sc_serv   ## Get Server PID

$ killall sc_serv  ## Stop server daemon

11. If you need a simplified command to start or stop SHOUTcast radio server, log in as root again and create the following executable script on /usr/local/bin/ path as in the example below.

$ su -
# vi /usr/local/bin/radio

Now add the following excerpt to the radio file.

#!/bin/bash
case $1 in
                start)
cd /home/radio/server/
./sc_serv &
              ;;
                stop)
killall sc_serv
                ;;
               start_daemon)
cd /home/radio/server/
./sc_serv daemon
               ;;
                *)
echo "Usage radio start|stop"
                ;;
esac
Create Shoutcast Execute File
Create Shoutcast Execute File

12. After the file was created, make it executable, exit root account, and a new command shout be available for your SHOUTcast radio server management.

# chmod +x /usr/local/bin/radio
# exit

13. To manage the server from now on, use radio command with the following switches.

$ radio start_daemon		## Starts SHOUTcast server as a daemon

$ radio start                   ## Starts SHOUTcast server in foreground

$ radio stop                    ## Stops SHOUTcast server
Start Shoutcast Server
Start Shoutcast Server

14. If you want to automatically start the server after reboot, but only on user login (in this case the server was installed on the local user named radio) issue the following command from radio account home path, then logout and login again to verify the functionality, as presented in the screenshot below.

$ whoami  
$ echo “radio start_daemon” >> ~/.bashrc
Start Shoutcast at Reboot
Start Shoutcast at Reboot

That’s it! Now, the SHOUTcast server is ready to receive sound or playlists from remote media players such as Winamp from Windows and Mixxx from Linux and broadcast all of the received audio content over the Internet.

If you liked this article, then do subscribe to email alerts for Linux tutorials. If you have any questions or doubts? do ask for help in the comments section.

If You Appreciate What We Do Here On TecMint, You Should Consider:

TecMint is the fastest growing and most trusted community site for any kind of Linux Articles, Guides and Books on the web. Millions of people visit TecMint! to search or browse the thousands of published articles available FREELY to all.

If you like what you are reading, please consider buying us a coffee ( or 2 ) as a token of appreciation.

Support Us

We are thankful for your never ending support.

53 thoughts on “How to Install SHOUTCast Radio Server (Online Media Streaming) on Linux”

  1. Hello, I am trying to setup an internet radio server. I have a system with CentOS 7 (1503). My knowledge of Linux is fundamental. Have followed your instructions step by step, with out changing a letter. When I got to step 2.7 and entered “netstat -tulpn | grep sc_serv’ at the terminal; the output I got from the system was: (Not all processes could be identified, non-owned process info
    will not be shown, you would have to be root to see it all.)
    Please help.

    Reply
    • If you started the ./sc_serv process from your own unprivileged username , then netstat command should display only the process name PID/Program Name table executed from your user space. The output with “Not all processes could be identified, non-owned process info
      will not be shown, you would have to be root to see it all” it’s kind of normal and informs you that your user does’nt have sufficient privileges to view all network processes, but only your own executed daemons.

      Reply
  2. Hi, I have it working perfect! But.. if I want the server to start on reboot without login? Sometimes my server is restarted and I have to manually start it, will be great if it starts by it self on reboot.

    thanks!

    Reply
  3. In step 7 to start the server execute sc_serv file from your current working directory
    in the example you have write:
    ./sc_serv.conf &
    the correct command is:
    ./sc_serv &

    Reply
  4. Got Error on step 2

    [[email protected] download]$ cp sc_serv ../server/
    [[email protected] download]$ cd ../server/
    [[email protected] server]$ ls
    sc_serv
    [[email protected] server]$ mkdir control
    [[email protected] server]$ mkdir logs
    [[email protected] server]$ ls
    control logs sc_serv
    [[email protected] server]$ nano sc_serv.conf
    [[email protected] server]$ ./sc_serv.conf &
    [1] 1727
    [[email protected] server]$ -bash: ./sc_serv.conf: Permission denied

    Reply
      • I managed to work out the problem when trying to start the server and getting a “permission denied” error (I found out why and how to fix it on the shoutcast website) here is what you need to do: enable the required access on the sc_serv file by doing ‘chmod a+x sc_serv’ after extracting it from the distribution file otherwise the OS is likely to not run it and will instead show the error message ‘./sc_serv: Permission denied’.

        It instead now shows an error which say “./sc_serv: cannot execute binary file”? does anyone know why this is happening?

        thanks.

        Reply

Got something to say? Join the discussion.

Have a question or suggestion? Please leave a comment to start the discussion. Please keep in mind that all comments are moderated and your email address will NOT be published.