You will recieve your password to this address. Address is not made public.

Your preferred username that is used when logging in.

RTMP cluster fails to failover Created Apr 20, 2009

This thread is solved

Views: 3497     Replies: 5     Last reply Aug 7, 2011  
You must login first before you can use this feature

Mist_

Posts: 2

Registered:
Apr 20, 2009

RTMP cluster fails to failover

Posted: Apr 20, 2009

My firewall only allows me to stream from port 80 on my streaming server, but I would like most users to connect to the standard RTMP port. I'm trying to use the cluster plugin to try each connection method in order.

The problem is probably that I can connect to the standard port, but because of the firewall I can't stream from it. The player connects to the first host, shows the message
200, Stream not found, NetStream.Play.StreamNotFound, clip:'[Clip] 'cam
and then tries to connect to the first host again.

These are the relevant parts (I think) of my code:

flowplayer("cam", "/gmaps/flowplayer31/flowplayer-3.1.0.swf", {
        clip: {
                autoPlay: 'true',
                provider: 'rtmp',
                url: 'cam',
                connectionProvider: 'cluster'
        },
        play: {
        },
        // streaming plugins are configured under the plugins node
        plugins: {
                rtmp: {
                        url: 'flowplayer.rtmp-3.1.0.swf',
                        live: true
                },
                cluster: {
                        url: 'flowplayer.cluster-3.1.0.swf',
                        connectTimeout: 500,
                        hosts: [
                          {host: 'rtmp://1.2.3.4/live'},
                          {host: 'rtmp://1.2.3.4:80/live'},
                          {host: 'rtmpt://1.2.3.4/live'},
                          {host: 'rtmpt://1.2.3.4:80/live'}
                        ],

If I change the first rtmp://1.2.3.4/live to rtmp://1.2.3.4:9999/live or some other port that does not respond at all the connect fails, then the player tries the next host line and everything works fine.

muvb14

Posts: 1

Registered:
Jun 18, 2009

» RTMP cluster fails to failover

Posted: Aug 26, 2009

Reply to: RTMP cluster fails to failover, from Mist_
Did you ever figure out a workaround for this issue? I am trying to do the same thing. A lot of my customers have port 1935 blocked on the firewall so it gives that error message instead of going to my backup port of 80.

I did find a unexpected but not quite good enough solution. Something on the client side is rolling over the ports trying to find a valid path to the file, first 1935, then 443, then 80 per wireshark. I'm not sure if its the web browser, flowplayer, or OS (vista). This takes too long though (about 8 seconds), before it goes to port 80 and is able to find the stream.

Mist_

Posts: 2

Registered:
Apr 20, 2009

RTMP cluster fails to failover

Posted: Aug 31, 2009

Reply to: » RTMP cluster fails to failover, from muvb14
No, I haven't found any good solution to my problem.

aigumnov

Posts: 36

Registered:
Apr 18, 2009

» RTMP cluster fails to failover

Posted: Aug 31, 2009

Reply to: RTMP cluster fails to failover, from Mist_
Currently, my site is running with the pre-release of the upcoming flowplayer-3.1.3 which fixes the problem at least for on-demand rtmp-streaming (and one doesn't need to use "clustering"). This feature was developed by my request.

lo95

Posts: 6

Registered:
Sep 8, 2009

» » RTMP cluster fails to failover

Posted: Nov 13, 2009

Reply to: » RTMP cluster fails to failover, from aigumnov
could you please tell us how you setup the player to have multi protocol (port) failover without "clustering"? I'm really interested in that feature.

Thanks