Streaming Video on Demand with nginx and RTMP Module

In this tutorial we will show a simple way to stream different types of video files using the Nginx server and RTMP modules.

Before starting the work, we will try to offer a small overview over the advantages of using RTMP versus HTTP video delivery.

Real Time Messaging Protocol (RTMP) was initially developed by Macromedia, for streaming on-demand and live media to Adobe Flash applications. It is a TCP-based protocol which maintains persistent connections and is defined as a “stateful” protocol. This means that from the first time a client connects until the time it disconnects, the streaming server keeps track of the client’s actions. On the other side, HTTP is a “stateless” application protocol used to deliver hypermedia information across the Internet worldwide.

Advantages of HTTP over RTMP:

  • Less likely to be blocked by firewalls at different levels in the network; RTMP uses default port 1935, which can be blocked sometimes, especially within corporate firewalls
  • Supported by more CDNs (it supports easier mirroring and edge caching)
  • More expertise in customizing HTTP

Advantages of RTMP over HTTP:

  • Ability to provide multicast support
  • Security and IP protection, using TLS/SSL or RTMPE
  • Seeking: particularly advantageous for long-duration content because the viewer doesn’t have to wait for the video file to load before jumping ahead, as is the case for HTTP-delivered video
  • Reconnect: if there is a network disruption, the client can re-establish a connection, while the video continues to play from the buffer; when the client re-connects, the buffer will begin filling to avoid any disruption in video or audio flow

And now, let’s start to build our streaming server.

To achieve this, we will compile the Nginx source code together with RTMP modules on a Ubuntu 12,04 box.

Logged in as root:

cd ~
mkdir nginx
cd nginx

Install the necessary software and dependencies:

# for compiler and git
apt-get install git gcc make

#for the HTTP rewrite module which requires the PCRE library
apt-get install libpcre3-dev

# for SSL modules
apt-get install libssl-dev

Clone Nginx RTMP module source code from Github:

git clone

Download the Nginx source code and extract it from the archive. At the time when we are writing this blog post, the current version is 1.4.3:

tar zxpvf nginx-1.4.3.tar.gz
cd nginx-1.4.3

Let’s compile Nginx:

./configure --add-module=/root/nginx/nginx-rtmp-module/ --with-http_ssl_module --prefix=/usr/local/nginx-streaming/
make install

Now it is the time to create a configuration file for Nginx. Go to:

cd /usr/local/nginx-streaming/conf
mv nginx.conf nginx.cong.bkp
nano nginx.conf

and paste the configuration below. This configuration is suggested by the documentation of the RTMP module.

worker_processes  1;

events {
    worker_connections  1024;

rtmp {
    server {
        listen 1935;

        chunk_size 4000;

        # video on demand for flv files
        application vod {
            play /var/flvs;

        # video on demand for mp4 files
        application vod2 {
            play /var/mp4s;

# HTTP can be used for accessing RTMP stats
http {
    access_log /var/log/nginx/access-streaming.log;
    error_log /var/log/nginx/error-streaming.log;

    server {
        # in case we have another web server on port 80
        listen      8080;

        # This URL provides RTMP statistics in XML
        location /stat {
            rtmp_stat all;
            rtmp_stat_stylesheet stat.xsl;

        location /stat.xsl {
            # XML stylesheet to view RTMP stats.
            # Copy stat.xsl wherever you want
            # and put the full directory path here
            root /var/www/;

        location /hls {
            # Serve HLS fragments
            types {
                application/ m3u8;
                video/mp2t ts;
            alias /tmp/app;
            expires -1;

To be able to see some nice statistics about the streaming, we must to copy stats.xml in the folder specified in the configuration above.

mkdir /var/www
cp /root/nginx/nginx-rtmp-module/stat.xsl /var/www/

And (re)start the Nginx server with:


It’s time to play!

As we defined in the Nginx configuration, the server can find some mp4 files in /var/mp4s or flv files in /var/flvs.

You can download an mp4 file here, right click and save it in /var/mp4s with the name sample.mp4.

Now, if you have a video player which supports RTMP protocol (eg: VLC), you can play it directly there.

From the VLC menu, Media->Open Network Stream.

In the URL field we input:


Where <IP_OF_THE_SERVER> is the IP or the hostname of the server where we installed Nginx.


And click play.


If you want to show this video on a website, you can use a flash player as Flowplayer or JW Player.

Below we will show how to use Flowplayer to achieve this. First we need to download flowplayer.rtmp-3.2.12.swf (see the download link at the bottom of the page).

The html code below shows how to implement RTMP using Flowplayer. You should just replace the /path/to/background.png, the <IP_OF_THE_SERVER> and the /path/to/flowplayer.rtmp-3.2.12.swf.

    <!-- flowplayer javascript component -->
    <script src=""></script>

<div id="player" style="width:644px;height:276px;margin:0 auto;text-align:center">
    <img src="/path/to/background.png" height="260" width="489" /></div>

$f("player", "", {
    clip: {
        url: 'sample.mp4',
        scaling: 'fit',
        provider: 'hddn'

    plugins: {
        hddn: {
            url: "/path/to/flowplayer.rtmp-3.2.12.swf",

            // netConnectionUrl defines where the streams are found
            netConnectionUrl: 'rtmp://<IP_OF_THE_SERVER>:1935/vod2'
    canvas: {
        backgroundGradient: 'none'

That’s all.

Of course the solution presented in the post above is minimalist and if you need to scale globally with your Video on Demand product, probably you need a CDN solution.


Symfony2 MSSQL support with pdo_dblib

We now maintain a library for connecting to a MSSQL database, since we are using it in one of our Symfony2 applications. You can find the code here:

If you are trying to use Doctrine 2 (for Symfony 2) to connect to MSSQL server from a Linux machine, you might encounter the same problems we did. To be able to connect to MSSQL from a Ubuntu Linux server you will have to install “php5-sybase” (Sybase / MS SQL Server module for php5).

$ sudo apt-get install freetds-bin php5-sybase

Add the following lines to “/etc/freetds/freetds.conf”, and make sure you set it to talk the right MSSQL protocol. The TDS protocol version should be 8,0 for MSSQL server 2005 and up, which may be confusing. Also replace “{mssql-server-ip-address}” with your MSSQL servers IP address (without the brackets).

        host = {mssql-server-ip-address}
        port = 1433
        tds version = 8.0
        client charset = UTF-8
        text size = 20971520

If you only connect to one server, you can also set the global TDS protocol version to 8,0 like this:

         # TDS protocol version
         tds version = 8.0

Now test that your freetds is working by using the command line client. You have to replace {username} and {password} with your username and password (without the brackets):

$ tsql -S mssql_freetds -U {username}
Password: {password}
locale is "en_US.UTF-8"
locale charset is "UTF-8"
using default charset "UTF-8"
1> quit

If you specify in “app/config/parameters.ini” that you want to use the “pdo_dblib” driver like this:


You will see the error:

The given 'driver' pdo_dblib is unknown, Doctrine currently supports only the following drivers:
pdo_mysql, pdo_sqlite, pdo_pgsql, pdo_oci, oci8, ibm_db2, pdo_ibm, pdo_sqlsrv

This is why you should install our LswDoctrinePdoDblib bundle, and following the instructions, you should comment out the “driver” and add a “driver_class” like this:

    # Doctrine Configuration
            #driver:   %database_driver%
            driver_class:   Lsw\DoctrinePdoDblib\Doctrine\DBAL\Driver\PDODblib\Driver

After that you should be able to run this command without any errors:

$ php app/console doctrine:database:create

Now do not expect everything to work flawlessly, since MSSQL is not officially supported, and Doctrine is very picky in what it does and does not accept as database structure. However, this should get you started. Post your experience and questions in the comments. Good luck!