Code 202

The `code202` error usually indicates that the streaming connection was interrupted or could not be maintained successfully.

In proxy mode, the stream is forwarded through a WebSocket connection in the following format:

```text
ws://<management-node-ip>/<render-node-ip>/10002
```

If this connection cannot be established, or becomes unstable during use, `code202` may occur.

## Cause 1: Network Disconnection or Incorrect Network Configuration

When the client cannot establish the required WebSocket connection, the most common causes are firewall rules, incorrect intranet IP settings, or incorrect public IP settings.

### Solution

#### Intranet Environment

- Check whether the firewall is disabled or configured to allow the required traffic.
- Verify that the local IP configured on the render node matches the actual intranet IP address.

Reference documents:
- [Standalone Intranet (Windows)](https://docs.paraverse.cc/doc/245/)
- [Cluster Intranet (Windows)](https://docs.paraverse.cc/doc/246/)

#### Public Network Environment

- Check whether the preferred public IP is configured correctly.
- Confirm that the external network can reach the configured public address normally.

Reference documents:
- [Standalone Extranet (Windows)](https://docs.paraverse.cc/doc/247/)
- [Cluster Extranet (Windows)](https://docs.paraverse.cc/doc/248/)

## Cause 2: Network Instability During Use

If the connection can be established initially but later drops during use, the issue may be caused by unstable network conditions in a private deployment environment.

### Solution

#### 1. Enable Delayed Stream Release in the Management Console

In the management console, go to:

**Application Management > Edit > General Advanced Settings**

Enable the delayed stream close setting and configure an appropriate delay period. The current draft states that the default value is `20s`. [page:13]

#### 2. Update `application.properties`

Modify the following parameters in `larkxr-center/application.properties` to extend the heartbeat timeout and reduce unnecessary task release during temporary disconnections.

```properties
# Default 12000 milliseconds to take a node offline without a heartbeat
# When task delay close is enabled, this can be changed to match the backend setting, for example 120000 (2 minutes)
pxy.clear-job.server-no-heartbeat-duration=120000

# Default 20000 milliseconds to close TaskInfo without a heartbeat
# When task delay close is enabled, this can be changed to match the backend setting, for example 120000 (2 minutes)
pxy.clear-job.taskinfo-no-heartbeat-duration=120000
```

After updating the configuration, restart the Admin service.

#### 3. Update the Web Front End if Needed

The current draft also provides front-end update packages for reconnection handling:

- Iframe: [datachannel.js](https://docs.pingxingyun.com/media/attachment/2025/03/datachannel.js)
- WebSDK: [websdk_resolve202.zip](https://docs.pingxingyun.com/media/attachment/2025/03/websdk_resolve202.zip)

## Cause 3: The Render Package Is Incomplete or Was Accidentally Deleted

The current page states that the rendering package may have been mistakenly terminated or removed, causing required files to be missing. [page:13]

### Solution

Re-download the program package and replace the contents of the `RenderServer` directory.

## Cause 4: Insufficient Hardware Encoding Channels on GeForce GPUs

When using a GeForce GPU, the number of available hardware encoding channels is limited by NVIDIA. The current draft notes that remote access tools such as Sunflower can also consume one encoding channel, which may contribute to the issue. [page:13]

### Solution

- Avoid occupying encoding channels with unnecessary remote desktop tools during use.
- For higher concurrency requirements, consider using Quadro or Tesla GPUs.
- If applicable, consider using the integrated hardware and software solution recommended by the vendor.

## Notes

- If `code202` appears immediately when launching, start by checking firewall rules, intranet IP settings, and public IP settings.
- If `code202` appears only after a session has been running for a while, investigate network stability and heartbeat timeout settings first.
- If the network path is normal, then check whether the render package is complete and whether the GPU encoding capacity is sufficient.