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 504
The `code 504` error indicates that the GPU on the rendering server does not meet the requirements for LarkXR cloud rendering. This is commonly caused by an unsupported GPU model, incorrect driver configuration, or insufficient hardware encoding channel capacity. ## Cause 1: The GPU Does Not Meet Configuration Requirements The rendering server's graphics card may not satisfy the required model support, driver version, or concurrency specifications for LarkXR. ### Solution Verify that the GPU meets all LarkXR hardware requirements, including supported GPU models, driver versions, and concurrent session limits. Refer to the official hardware requirements documentation for details: [LarkXR GPU Requirements](https://www.pingxingyun.com/online/sr3_2.html?id=384) ## Cause 2: Insufficient Hardware Encoding Channels on GeForce GPUs GeForce-series GPUs have a limited number of hardware encoding channels due to NVIDIA's own restrictions. Remote management tools such as Sunlogin or other similar software also consume encoding channels, further reducing the number of available concurrent sessions. Depending on the GPU model, GeForce cards typically support only 2 to 3 concurrent hardware encoding sessions. NVIDIA drivers version 531.61 and later support up to five concurrent sessions. ### Solution Avoid using GeForce-series GPUs for LarkXR rendering deployments. Use a professional-grade GPU (such as an NVIDIA Quadro or Tesla series), or use a LarkXR hardware-software integrated machine that is pre-configured for cloud rendering workloads. Reference: [NVIDIA Video Encode and Decode GPU Support Matrix](https://developer.nvidia.com/video-encode-and-decode-gpu-support-matrix-new) ## Notes - GeForce GPUs are not recommended for production cloud rendering environments due to their hardware encoding channel limitations. - If remote management tools are in use, account for the encoding channels they consume when calculating available concurrency. - Always verify driver version compatibility before deployment.
admin
2026年5月12日 11:08
转发文档
收藏文档
上一篇
下一篇
手机扫码
复制链接
手机扫一扫转发分享
复制链接
Markdown文件
Word文件
PDF文档
PDF文档(打印)
分享
链接
类型
密码
更新密码
有效期