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 502
The `code 502` error indicates that the stream push from the rendering server timed out. This is typically caused by an application that takes too long to start on the local rendering server, or by the application failing to launch locally on the rendering server altogether. ## Cause 1: The Stream Push Timed Out If the application on the local rendering server takes too long to start, the stream push may exceed the default timeout threshold and trigger a `code 502` error. ### Solution Open the **Rendering Service Manager** and increase the streaming timeout value to `300000` (milliseconds). This allows more time for slow-starting applications to initialise before the connection is dropped. ## Cause 2: The Application Cannot Be Started Locally on the Rendering Server If the application fails to launch locally on the rendering server, no stream can be established, resulting in a timeout error. ### Solution Connect to the rendering server using a remote management tool (such as Sunlogin, TeamViewer, or VNC) and attempt to launch the application locally. Observe whether the application starts successfully and check for any error messages or missing dependencies. ## Notes - If the application starts locally but the error persists, consider increasing the streaming timeout value further. - If the application fails to start locally, resolve any application-level issues on the rendering server before retrying.
admin
2026年5月12日 11:07
转发文档
收藏文档
上一篇
下一篇
手机扫码
复制链接
手机扫一扫转发分享
复制链接
Markdown文件
Word文件
PDF文档
PDF文档(打印)
分享
链接
类型
密码
更新密码
有效期