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
-
+
首页
Cloud Application Exit Detected
When the web client displays a "Cloud application exit detected" notification, it means the rendering application on the server has terminated unexpectedly or has been closed. This can occur due to several configuration or hardware-related issues. ## Cause 1: The Application Is a Multi-Process Application Some applications spawn multiple processes at runtime. If the rendering service is monitoring only the primary process and that process exits or hands off control to a child process, the service may incorrectly interpret this as an application exit. ### Solution Enable **Exclusive Mode** in the Rendering Service Manager for the application. This mode ensures that the rendering session is bound to the application's full process lifecycle rather than a single process entry point. ## Cause 2: Incorrect UE Program Execution File Path The Unreal Engine (UE) application executable path configured in the rendering service is incorrect. If the service cannot locate the correct executable, it may launch the wrong process or fail to monitor the application properly. ### Solution Set the UE program execution file path correctly in the Rendering Service Manager. Refer to the following guide for detailed configuration steps: [How to Set the Application Path](https://www.pingxingyun.com/contribute/detail?topicId=10107&categoryId=3) ## Cause 3: Rendering Node Uses a GT-Series Graphics Card GT-series graphics cards (typically entry-level NVIDIA cards) are not supported by LarkXR's rendering service. Using an unsupported graphics card will cause the rendering application to fail or exit immediately. ### Solution Replace the graphics card on the rendering node with a supported model. Refer to the following page for the list of supported hardware: [Supported Graphics Cards](https://www.pingxingyun.com/online/sr3_2.html?id=384) ## Cause 4: Application Crash or Unexpected Exit The application itself may be crashing or exiting on the server side due to internal errors, missing dependencies, or runtime exceptions. ### Solution Connect to the render server directly and attempt to launch the application locally to verify whether it runs stably. Review any crash logs or error dialogs to identify the root cause of the unexpected exit. ## Notes - If the application is multi-process, always enable Exclusive Mode to ensure proper session monitoring. - Verify hardware compatibility before deploying a new rendering node to avoid graphics card-related failures.
admin
2026年5月12日 11:10
转发文档
收藏文档
上一篇
下一篇
手机扫码
复制链接
手机扫一扫转发分享
复制链接
Markdown文件
Word文件
PDF文档
PDF文档(打印)
分享
链接
类型
密码
更新密码
有效期