If successful, you should see the NGINX default page:Įdit the nf file as follows: nano /etc/nginx/nginx.
Configuring nginx to work with stunnel install#
Then install NGINX: sudo apt-get install nginx sudo apt install libnginx-mod-rtmpĪt this point you can test that NGINX has been installed correctly by testing with your browser:
Configuring nginx to work with stunnel update#
Update all packages: # sudo apt-get update # sudo apt-get upgrade The machine was duly created and connected via SSH to its IP shown in the portal. Once the VPS was provisioned, we selected the Ubuntu 18.04 LTS install image. Research suggested that RTMP streaming/multiplexing is not particularly CPU/RAM intensive and is more about bandwidth consumption. We opted for a 1 x vCPU, 2GB RAM, High-Frequency machine with 64GB SSD storage, and 2TB monthly bandwidth. Nginx will have to multiplex the connection and either provide normal web-content. It turns out the solution has been relatively straightforward… Our solution:įirstly, we signed up for a new VPS with We will use stunnel on our client to connect to the nginx on our server. However, for me, an issue with a shared service leaves a sour taste and so began the journey to discover what would be involved in running our own RTMP server. Fortunately, we were quickly able to flip to sending our stream directly to YouTube and our broadcast worked successfully. Then, the second week about 10 minutes before due to go live restream.io suffered an outage. We tested with OBS sending the stream to restream and for the first week, everything worked fine. Initially, the plan was to stream from OBS Studio to an intermediate platform, restream.io Issue:ĭuring the Coronavirus season, our church, like many, ventured into the world of streaming services, primarily to YouTube but with an eye to multiplexing to both YouTube and Facebook at the same time. For details about stunnel key management, see Managing disk encryption keys. possible to use a SSL proxy like nginx but we already have stunnel running :thinking. /etc/siq/ssl/client.crt, /siq/svc/nginx/ssl.conf, Run the certcfg utility as. Install it open configuration file nf from installation pathstunnelconfig directory At the end of the file put the next part of the code. stud and nginx gets similar performance but, as you can see on the bottom plot (whose scale is logarithmic) stud starts with an initial latency of 40 ms. However, early latency issues of nginx has been solved, thanks to the change in configuration. I’m writing these notes up, mainly as a reference for me in the future – but they might just help others looking to do similar. This example was created during the LDAPS-connection of WebUntis. Like in previous benchs, stunnel is not able to scale, with a maximum of 400 TPS.
0 kommentar(er)
