The following instructions assume that you have root access (sudo on most distributions) to a GNU/Linux server, and are familiar with basic command line tasks.

The recommended Libretime server platform is Ubuntu 16.04 LTS (Xenial Xerus).

The server should have at least a 1GHz processor and 1GB of RAM, preferably 2GB RAM or more. If you are using a desktop environment and web browser directly on the server you should install at least 2GB RAM, to avoid swapping to disk.

The LibreTime installation does not use much disk space, but you should allow plenty of storage capacity for the Libretime library. A hot-swap RAID array is recommended for media storage, in case of disk failure. You should also consider a UPS or other battery-powered system to offer some protection against short-term power failures.

LibreTime depends on infrastructure and services that need to be configured properly for it to run smoothly. This chapter will go through the individual parts of a LibreTime install and help you assess how you need to manage them.


LibreTime should only be run on a Server behind a firewall. This can either be a dedicated firewall in the network (like on some cloud providers) or a local firewall running iptables (as you would use on a root server or a local machine).

Setting up a local firewall is done differently on all the supported distros.

There is a vast amount of ways to configure your network, firewall included. Choose the way that best fits your deploy and dont internal expose parts of your LibreTime install on the network.

The following ports are relevant to the deploy and need to be opened to varying degrees.

Port Description
80 Default unsecure web port. Needs to be open for the webserver to serve the LibreTime webinterface or if you enable TLS a redirect to the secure web port.
443 Default secure web port. This is where your LibreTime webinterface lives if you choose to configure TLS.
8000 Main Icecast instance. This is where your listeners connect if you plan on using your LibreTime server to directly serve such connections. You can also configure external Icecast or ShoutCast instances for this later.
8001 and 8002 Master and Show source input ports. Only open these ports if you plan on letting anyone use these features. You might want to consider usinga fixed IP if you use the master source for studio connections on port 8001 and only allow DJ to connect over a VPN link or similar depending your security needs.

The remaining parts of LibreTime might open additional ports that should not be accessible from any untrusted networks. You should consider how to configure their firewall access individually once you configure them.


You should set up PostgreSQL properly according to the instructions for your distro. Distro provided packages are fine for LibreTime as it does not have any specific version dependencies.

You should restrict access to the database and create a user specific to LibreTime. The default installer script create a user with the passwordairtime which is far to open and should be replaced with a self provided user and a secure password. See the PostgreSQL docs on roles and databases.

Please take care to ensure that your database is properly backed up at regular intervals. LibreTime uses the database to store your schedule, settings, playout history and more. See backing up the server for more information on this.


LibreTime uses RabbitMQ interfacing various components like the main interface and parts of the system like the audio analyzer and podcast downloader as well as the playout system through a common message queue. Again, the version provided by your distro will probably work fine for all LibreTime is concerned.

The install script sets airtime as the password on the default user. It is recommended to provide your own user using a secure password.

You can use rabbitmqctl or the Management Plugin to manage your RabbitMQ users.

There is no state in the RabbitMQ system that you need to backup but you want to ensure that your RabbitMQ configuration and user permissions are safe.

RabbitMQ hostname

RabbitMQ requires a fixed and resolvable hostname (see the docs), which is normal for a server. For a desktop or laptop machine where the hostname changes frequently or is not resolvable, this issue may prevent RabbitMQ from starting. When using a desktop or laptop computer with a dynamic IP address, such as an address obtained from a wireless network, the rabbitmq-server daemon must not start up before the NetworkManager service or

You may also choose to configure RabbitMQ to only listen on the loopback interface with a localhost node name. You can use environment variables or a configuration file to do this.

See these links for more information:

Beware, Here be dragons!

The following instructions have been taken verbatim from the Libretime docs and not been brought up to date.

Sound cards

If your Libretime machine will only be used to stream directly to an Icecast or SHOUTcast streaming media server, you do not require a sound card to be installed on the Libretime server side. This option is suitable for Libretime installations at your ISP's data centre, remote from any transmitter. However, you will not be able to take advantage of Libretime's live show recording feature (yet).

If you intend that your Libretime server will have a direct audio output to a broadcast transmitter or a separate stream encoder, your server machine must have a sound card supported by an ALSA driver. Almost all standard sound cards have ALSA drivers built into the Linux kernel, which do not need to be installed separately. If in doubt about driver support for your sound card, check the ALSA support matrix at:

USB audio device index

Some server motherboards do not have a default ALSA device (index number zero, shown as hw:0,0 in ALSA notation), and a USB sound card is often prevented from getting index zero by the GNU/Linux distribution's configuration. This setting may be in a file such as /etc/modprobe.d/alsa-base.conf in Ubuntu, which can be edited with nano:

sudo nano /etc/modprobe.d/alsa-base.conf

Comment out the lines beginning options snd-usb- to fix the problem:

# Prevent abnormal drivers from grabbing index 0

# options snd-usb-audio index=-2
# options snd-usb-us122l index=-2
# options snd-usb-usx2y index=-2
# options snd-usb-caiaq index=-2

Save the file with Ctrl+O and close nano with Ctrl+X. Then remove and re-insert the cable connecting the USB sound card to the server (making sure any mixer or amplifier connected is faded down, to avoid a 'thump' on the output). The command aplay -l should now confirm that the USB Audio device has index 0 (shown as card 0, device 0):

aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: MobilePre [MobilePre], device 0: USB Audio [USB Audio]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

When using a USB sound card with ALSA, some how-to documents advocate setting the nrpacks=1 option, but this is not recommended for Libretime because it can increase CPU load significantly.

Intel HDA mixer labels

If you have an Intel HDA sound card, as built in to many contemporary motherboards, you may discover that the recording controls in alsamixer have incorrect labels. This problem can make it difficult to adjust mixer levels except by trial and error. To fix these labels, you can pass a specific model= parameter to the snd-hda-intel module of the Linux kernel. On Debian or Ubuntu GNU/Linux, you can do this by first identifying the model you have, with the command:

cat /proc/asound/card0/codec* | grep Codec

The server should respond with a line such as:

Codec: Realtek ALC882

Referring to the appendix HD Audio Models in this book, find the matching codec and model. In this example, the codec is ALC882 and the motherboard has six analogue jacks and two S/PDIF sockets, so the model is 6stack-dig.

  3stack-dig    3-jack with SPDIF I/O
  6stack-dig    6-jack digital with SPDIF I/O

Edit the file /etc/modprobe.d/alsa-base.conf with nano as follows:

sudo nano /etc/modprobe.d/alsa-base.conf

Add an appropriate line for your soundcard model to the end of the file, such as:

# Realtek ALC882
options snd-hda-intel model=6stack-dig

Save the file with Ctrl+O and close nano with Ctrl+X. Then reboot the server. After the reboot, you should now see that the mixer controls are correctly labelled.

Disable desktop and other sounds

If you are installing Libretime on a desktop computer, make sure you disable or remove any programs that could send unintended audio to a sound card you are using for broadcast output. This includes alert sounds which play when the computer is ready for use, or when a user logs in. On Ubuntu, these sounds are configured using System -> Preferences -> Sound on the main desktop menu. (This configuration tool only works when the PulseAudio sound server is installed).

You may prefer to remove all system sound files from the computer, in case they could be played unintentionally via the sound card. For example, on Ubuntu you may wish to remove the ubuntu-sounds package, with the following command:

sudo apt-get purge ubuntu-sounds


The PulseAudio sound server is not recommended for Libretime sound card output, but is installed by default on Ubuntu. To remove PulseAudio from an Ubuntu machine, type the following command:

sudo apt-get purge pulseaudio

Removing the pulseaudio package on a desktop Ubuntu machine may force the removal of the ubuntu-desktop metapackage. However, this metapackage is only installed on the system for managing upgrades; removing it does not remove the entire desktop.

After removing PulseAudio, if your Libretime machine has a desktop, you can install a mixer applet which can control the ALSA soundcard driver directly, such as gnome-alsamixer:

sudo apt-get install gnome-alsamixer

On a server with a sound card but without a desktop, you can control sound input and output levels using the command line program alsamixer:

This program should already be installed on an Ubuntu or Debian machine with a sound card. If not, you can install it with the command:

sudo apt-get install alsa-utils

The PHP cache

This dependency, introduced in Libretime 2.5.0, can improve the responsiveness of the Libretime administration interface and reduce server load. Various PHP cache software is available, but the current cache software required by Libretime is APC ( You should uninstall or disable any other PHP cache that may be present on the server, such as XCache, before installing Libretime and APC. This is because having multiple caches enabled can cause problems for PHP.

You can remove the XCache package php5-xcache from a Debian or Ubuntu server with the command:

sudo apt-get remove php5-xcache

APC is available in Debian or Ubuntu as the php-apc package. If you already have Apache installed on the server you are going to use for Libretime, you can install APC and get it working with the following commands:

sudo apt-get install php-apc
sudo invoke-rc.d apache2 restart

APC has an administration page, which is not installed by default. If you wish, you can install and configure it with the following commands:

sudo cp /usr/share/doc/php-apc/apc.php /usr/share/airtime/public/
sudo nano /usr/share/airtime/public/apc.php

You should set an admin password for the apc user on line 42 of the file, such as mynewpassword in this example:


Save the apc.php file with Ctrl+O and close it with Ctrl+X. Then open a web browser at the apc.php page of your Libretime server, such as:

You will then be able to confirm that APC is working, and view some statistics for the cache.

Remove webmin, if installed

The webmin control panel ( has been known to remove Apache and PHP packages on Debian and Ubuntu systems, which can cause the Libretime package to be removed in turn. This problem is easily reversed by re-installation of the affected packages, but it has the potential to disrupt your broadcast playout from Libretime. Webmin is not likely to be installed on your server unless your system administrator has installed it manually. This is because webmin was removed from official Debian and Ubuntu package repositories some years ago.

RabbitMQ on Debian squeeze

In Debian 6.0 'squeeze' the rabbitmq-server daemon does not start automatically after a reboot. This should be fixed before installing Libretime, to prevent problems at playout time. If the rabbitmq-server package was installed before the last reboot, you will need to run:

invoke-rc.d rabbitmq-server start

as the root user before the installation of Libretime. If it is not already installed, run the following command as root:

apt-get install rabbitmq-server

After a fresh installation, rabbitmq-server will start automatically, so there is no need to run the invoke-rc.d command mentioned above.

In either case, you should then edit lines 13 and 14 of the file /etc/init.d/rabbitmq-server (as root) to show:

# Default-Start:     2 3 4 5
# Default-Stop:      0 1 6

and then run the command (as root):

update-rc.d rabbitmq-server defaults

This should make sure that rabbitmq-server starts after the next reboot.