Skip to content


Flussonic Media Server can connect to another Flussonic Media Server (peer), take list of running and available ondemand streams and route clients to proper peers using cluster peering mechanism.


You can set Flussonic Media Server peer:

cluster_key abcd;
peer streamer:8081;

You need to set same cluster_key on all cluster hosts.

Flussonic cluster peering

You can set multiple peers:

cluster_key abcd;

All peers can have different streams, Flussonic Media Server will route clients to proper peers.

Private and public addresses of peers

When the peer Flussonic servers are in the local network and in the settings you use the private addresses (hostnames) that are necessary for the communication of peers within the local network, these internal addresses can appear on the clients that playback a stream.

You can expose only the public addresses of peers, at the same time allowing them to use private addresses when communicating within a cluster. To do so, add in the settings of each peer the public option, which specifies the public address of this peer server:

cluster_key abcd;
peer streamer:8081 {
    public streamer.public;

When redirecting to, Flussonic will use the protocol, HTTP or HTTPS, that was configured for this peer.


Flussonic Media Server will redirect clients to peers when you ask for a stream.

It is a very important difference between peer and source, because source is designed for moving data via a dedicated channel from origin to edge.

Peering is designed for situations when client can take video stream from any server in a group, so servers (peers) in a group talk to each other and tell what streams do they have.

When client connects via HLS, HTTP MPEG-TS, RTSP, RTMP or opens embed.html to any of servers in a group,it may redirect to another server where this stream is really located.