1/2/2023 0 Comments Instafeed rtmpLuckily, you don't have to push the stream from the application with the key, but you can also pull it from the public application ( /live). However, this still causes problems, as you'd push the stream from the same IP than the clients that are using it, but you can't allow them to publish to your stream. This means your access control would be limited to the key, alone, but at the same time it's less of a problem, as it's transmitted encrypted. from the 127.0.0.1, you can't use the allow/ deny directives to limit connection based on IP addresses anymore. As you can't renew the Let's Encrypt ertificate using RTMP, you might need a HTTP server block for the HTTP-01 challenge, too.Īs the connection to Nginx always comes from the stunnel i.e.The Nginx should be listening for RTMP on local loopback, port 1936/tcp.The stunnel configuration could look like this: Ĭert=/etc/letsencrypt/live//fullchain.pem Without that, the client defaults to no, which is the server mode. the stunnel is working as a plain text server and TLS client, which is configured with client = yes. The examples on the Internet are mostly RTMP→RTMPS i.e. Yes, this is possible with stunnel, as RTMPS is just a RTMP session wrapped inside a standard TLS session. However, I've added an improved version for more fine-tuned access control, and I recommend using the configuration from it, instead. UPDATE: This is my original answer that describes pretty well the issues one may face while implementing RTMPS with Nginx.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |