Scenario: The cloud rendering server cannot be directly accessed from the external network, but can be accessed through machines within the same local area network. By utilizing Nginx's reverse proxy mechanism, the network topology can be implemented as follows:
To achieve this setup, ensure that the Nginx server is running on a Linux operating system to support UDP port reverse proxy functionality.
Following the above network topology, deploy it using a cluster deployment method. Please refer to the deployment guide for Cluster Intranet and select "Enable websocket proxy." After deploying the intranet, install Nginx on servers connecting the external network and intranet. After completing the Nginx deployment, follow the steps below:
Step 1: Modify Nginx configuration to set up reverse proxies for TCP and UDP ports
Add a reverse proxy for port 8181: Download out.conf and place it in the
nginx/conf/conf.ddirectory. Make sure to modify the IP address in the second line of the file to the actual IP address of the central management node.Add a reverse proxy for UDP ports: Download udp.conf and place it in the
nginx/confdirectory. The UDP port numbers should match the UDP port range configured in the rendering node startup manager and correspond one-to-one. For example, if the rendering service manager configures a port range of 10011-10020, you need to set up reverse proxies for 10 UDP ports.Modify the
nginx\conf\nginx.confconfiguration file and add the following configuration item: include configuration files.
Step 2: Open Nginx server's port 8033 and UDP port range, and verify the configuration
Verify the configuration by accessing the Nginx server's IP address followed by port 8033 (the port number can be modified in the 7th line of out.conf).
For example, visit: http://222.12.20.19:8033. You should successfully access the application overview and be able to enter applications for rendering.
