LarkXR Troubleshooting Reference
Deployment
Troubleshooting Backend Intranet Access Failure
Troubleshooting Backend External Access Failure
Troubleshooting Database Startup Failure
Troubleshooting Black Screen on Server Startup
Troubleshooting Service Startup Failure
Cluster Edition (Linux)
Troubleshooting “not found” Errors in sh Startup Scripts
Public Cloud
Tesla GPU GRID Driver and License Requirements
Configuring a Virtual Display for the Second vGPU
Troubleshooting Resolution Below 1080p on Tesla GPUs
Error Code Explanation
Web Client
Troubleshooting “No available render server, Please try again later.”
Code 102
Code 103
Code 202
Code 203
Code 401
Code 402
Code 403
Code 404
Code 500
Code 501
Code 502
Code 504
Code 601
Stuck on 5/5 Loading Page
Cloud Application Exit Detected
Point-to-Point Connection Disconnected
Frontend & Backend Inaccessible
VR Client
Code 11
Code 900
Code 1001
Continuous Loading
UDP Connection Failure
Other Issues
Code 1002
AR Client
UDP Connection Failure
Secondary Development
Data Channel
Unable to Communicate — Troubleshooting Guide
Failed to Pass the Message Body
Incorrect Message Delivery
Delay in Receiving Messages
UE5 Plugin Packaging: Possible Reasons for "Unknown Cook Failure"
WebSDK
1-5 Cards Loading
SDK License Does Not Exist
vue2-react Running Error (Node v18.12.1)
H.265 WebCodec Not Supported by Browser
Interface call
No Access Permissions
Signature and Timestamp Cannot Be Empty
Invalid Key Pair
Others
Apps Can't Sync
LarkXR Launcher: Check Environment Error
User Experiences
Live Streaming Screen is Black
Picture Quality is Not Clear
SN
Local SN
Invalid Authorization Code
Cloud SN
Authorization Code Is Disabled
Authorization Code Does Not Exist
-
+
首页
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.  ## 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.
admin
2026年5月8日 17:50
转发文档
收藏文档
上一篇
下一篇
手机扫码
复制链接
手机扫一扫转发分享
复制链接
Markdown文件
Word文件
PDF文档
PDF文档(打印)
分享
链接
类型
密码
更新密码
有效期