FlashDreams Lingbot-World docs now cover asset staging, disk usage, VRAM, and first-run behavior, but they still do not clearly document the WebRTC media-path networking requirements.
On cloud GPU instances where users only have SSH/TCP forwarding, the HTTP viewer page may load, but WebRTC media can still fail because the browser/server peer connection needs appropriate WebRTC connectivity.
Requested work:
- Document that Lingbot-World WebRTC requires a working WebRTC media path, not just access to the HTTP /request_session page.
- Explain limitations of SSH/TCP-only forwarding for WebRTC media.
- Add guidance for supported remote setups, such as direct network access, proper UDP forwarding, VPN, or TURN/STUN if applicable.
- Add a troubleshooting note for “viewer loads but video never appears.”
Acceptance criteria:
- Users can tell before launch whether their remote/cloud setup supports Lingbot-World WebRTC.
- The docs explain what to check when the page loads but media does not stream.
FlashDreams Lingbot-World docs now cover asset staging, disk usage, VRAM, and first-run behavior, but they still do not clearly document the WebRTC media-path networking requirements.
On cloud GPU instances where users only have SSH/TCP forwarding, the HTTP viewer page may load, but WebRTC media can still fail because the browser/server peer connection needs appropriate WebRTC connectivity.
Requested work:
Acceptance criteria: