Stand-Alone External Network

After successfully running the on-premise deployment process, configure the external access policy, which includes two configuration modes: direct connection mode and proxy mode. Understand the difference between direct connection mode and proxy mode

Direct Connection Mode

Since the standalone master node and rendering node are deployed on the same machine, the system defaults to the direct connection mode. If the server has an external IP, external access can be achieved through port opening or router port mapping. It is recommended to use the proxy mode when configuring HTTPS access; otherwise, the rendering node needs to configure an SSL certificate to use the WSS protocol.

Configuration Steps:

1. Double-click on LarkXRLauncher.exe to run it and click on configure rendering node.

   • Set "Local IP" to the internal IPv4 address.

   • Set "Public IP" to the external IP.

   • Set "Preferred Public IP" to the external IP (e.g., 112.6.266.122).

   Refer to the image below:

Network Port Opening/Mapping Strategy

Proxy Mode

In the standalone version, you can choose to use the proxy mode without the need to open an additional 10002 port.

Configuration Steps:

1. Double-click on LarkXRLauncher.exe to run it and click on configure management node.

   • Enable the rendering server connection proxy.

2. Click on configure rendering node.

   • Set "Local IP" to the internal IPv4 address.

   • Set "Preferred Public IP" to the external IP (e.g., 112.6.266.121).

   Refer to the image below:

Network Port Opening/Mapping Strategy