Topic: mod_rewrite question

[rayj2018]

Can a mod_rewrite rule take an incoming rtmp and forward it to a co-located container?

I have an Ubuntu 16.04 host server with 4 LXD containers.
The containers are duplicate media servers.

So how this would work is like this:

A user initiates an RTMP stream from a video broadcasting app. The rtmp stream comes into the host and it is then routed to one of the containers, based on the URL. For instance rtmp://"IP":1935/lpc1 would eventually route to container 1 at the IP. Of course the container is a different IP than the host.

Can this be done?

Thanks,

Ray

[admin]

Please use a meaningful, specific subject. See Forum Rules

[ray2018]

[mraddi]

Hello Ray,

I'm not sure if apache is able to handle RTMP-streams.
For this I have used NginX (free - compiled with RTMP-module) or Wowza (which is not free ).

Best regards
Matthias

[ray2018]

So if I use nginx w/rtmp module, can I then re-direct an incoming rtmp stream to another server?

Thanks,

Ray

[mraddi]

Hello Ray,

I've compiled NginX with RTMP-module and used the following configuration:

[ray2018]

Thanks for taking the time to respond. I appreciate it.

So, how would the stream settings in OBS for instance be set to tell nginx/rtmp to pass the rtmp on to another server? And how would the nginx config look to accomplish this?

Thanks again,

Ray

[mraddi]

Hello Ray,

I've never used OBS up to now so I can't tell if/how you need to configure this software.
But from my point of view you don't have to configure anything special on the backend-(OBS-)systems that are behind a reverse-proxy (the same as you don't need special configuration on webservers that are behind a reverse-proxy-server).

Just to verify that I got your problem correctly:
* you have one big master-server connected to the network
* you have four (containered) RTMP-servers (live or VideoOnDemand?) in the backend that should be available via the one hostname/ip-address of the master-server

But why use four RTMP-servers instead of one? As it is containered the same phyiscal server has to bear all the load so distributing the load between different servers couldn't be the reason.
NginX (and Wowza - the two RTMP-servers I've used up to now) are able to handle more than one stream at the same time - either with different stream-names (/live/stream1, /live/stream2, ...) or within different paths (/live1/stream, /live2/stream, ...).
But I guess there are reasons you created your environment the way you did .

You can either
a) combine the four instances ob OBS into one (if possible) available directly on the master-server
b) or run NginX on the master-server and configure it according to the example already provided to run as a RTMP-repeater.
For b) I would suggest the following steps:
* ensure that NginX is already compiled with the RTMP-module or compile NginX yourself with this module
* configure it to server a RTMP-stream directly from an mp4-file on the harddrive - see the "vod"-part in the config-snippet I've posted some days ago - just as a test to ensure that NginX itself is running as expected able to server RTMP-stream-data
* afterwards you can add the configuration for every backend-OBS-server, which might look similar to this (just a guess because I don't know if you are serving live-RTMP-data and of course I don't know the stream-names/paths you are using on the backend-servers):

[ray2018]

Thanks for the response mraddi.

So would the config you posted work for live video?
I thought the "pull" was for mp4 videos?

Thanks

Ray

[ray2018]

I am using 4 containers that will be used by 4 separate live video streamers. So one broadcaster would essentially be the "owner" of one container. Another broadcaster would "own" another container, and so on.

Ray