Code 102

The `code102` error usually indicates that the client cannot establish the required connection to the render node, or that the cloud application failed to start correctly on the rendering server.

## Cause 1: Port 10002 Is Not Accessible

When external network access is configured, port `10002` may be inaccessible. If this port cannot be reached, the client may fail to connect properly and trigger `code102`.

### Solution

Use one of the following methods:
- Enable proxy mode.
- Open TCP port `10002` on the rendering node.

![Port 10002 configuration example](https://docs.paraverse.cc/media/202504/835e3a81c70343058745b24ac75703b01822.png)

## Cause 2: The Application Failed to Start on the Rendering Server

The error may also occur if the target application does not start successfully on the rendering server.

### Solution

Log in to the rendering server and test whether the application can be launched directly. If the application cannot start normally on the server itself, resolve the application startup issue first.

## Cause 3: Another Application Is Causing a Conflict

Some applications running on the rendering server may conflict with the cloud application. The current page specifically mentions software such as Unreal Engine development tools and Youdao translation software as possible examples. [page:11]

### Solution

- Close unnecessary applications running on the rendering server.
- Pay special attention to development tools, overlays, translation tools, or other software that may hook into graphics or input resources.
- If the conflicting application cannot be identified, restart the rendering server and test again.

## Notes

- Start by checking network connectivity for port `10002`, because this is the most direct cause listed in the current article.
- If the network path is normal, verify whether the application itself can start successfully on the rendering server.
- If both checks pass, investigate software conflicts on the server.