Nginx proxy for UE multi-instance cloud rendering

Nginx Https Proxy

We mostly use the http protocol when implementing UE pixel streams, but sometimes the front end needs to use the https protocol due to some functional problems (such as the front end calls the local camera) and needs to use the https protocol. If the http request is used internally at this time, it will be blocked. One easy solution is by modifying your browser's security settings.

1 modify chrome

  1. Click the icon to the left of the chrome url to enter the https settings (Site settings)
  2. Found: Insecure content, change block to Allow
  3. Chrome will remind you to reload, just click reload

2 Solved by Nginx proxy

In some cases, the front end needs to use the https protocol to call the camera, and https usually cannot send http requests (for some static resources, but not for interface services). The corresponding websocket ws request should also be converted to a wss request.

1. Configure SSL certificate

To directly use the https setting of the pixel stream plug-in, you need to apply for an SSL certificate ( https://www.joyssl.com/certificate/ ) on each cloud rendering server. Generally, a fee is required for applying for a certificate. It is a bound domain name, and different domain names require different certificates (the domain name is identified as a unique value). But for UE's multi-instance cloud rendering, it is unrealistic to bind a domain name to each server. Therefore, nginx is needed to implement the reverse proxy for http.

2. Configure nginx

Nginx is used as a high-performance HTTP and reverse proxy web server. nginx tutorial (

Guess you like

Origin blog.csdn.net/qq_33377547/article/details/128256933