Share your bug report, feature request, or comment.
Currently we can only specify the webserver to listen on localhost, enabling the use of a SSL/TLS reverse proxy.
But it's currently not possible to use a proxy like stunnel to do the same thing with the RTMP protocol without also keeping the unencrypted version open to all interfaces.
Using a tool like stunnel can prevent stream tokens from being leaked to anyone able to intercept the RTMP packages.
I've already used stunnel in conjunction with nginx-rtmp, for both the inbound and outbound connection.
Share your bug report, feature request, or comment.
Currently we can only specify the webserver to listen on localhost, enabling the use of a SSL/TLS reverse proxy.
But it's currently not possible to use a proxy like stunnel to do the same thing with the RTMP protocol without also keeping the unencrypted version open to all interfaces.
Using a tool like stunnel can prevent stream tokens from being leaked to anyone able to intercept the RTMP packages.
I've already used stunnel in conjunction with nginx-rtmp, for both the inbound and outbound connection.