TROUBLESHOOTING

Identify the failing stage before changing settings

Connection errors, dropped streams, black picture and missing sound are different symptoms. Start with the matching checks, keep a known working configuration and change one major variable at a time.

Cannot connect: inspect the account and key

Check account login, eligibility and the current session’s address/key pair. Update the instance that is actually running, not another window. Capture the error text and time without exposing the full key.

  • Match account, session and OBS instance.
  • Do not repeatedly retry an unverified old key.

Disconnecting: separate network and encoding load

Inspect dropped frames and encoding pressure. Check competing uploads for network issues, or resolution, frame rate and scene complexity for processing limits. With multiple instances, test one simple stream first and restore others gradually.

  • Observe total bandwidth and hardware use.
  • A concurrency-related failure still needs its specific bottleneck identified.

Black picture or no sound: verify inputs

Check the active scene, source visibility, capture permissions and device availability. Test microphone and media audio individually, including mute state and duplicate capture. Record your system, version and recent changes to make the issue reproducible.

Frequently asked questions

Should I reinstall first?

Check parameters, permissions, network and inputs first. Reinstallation does not fix every eligibility or network issue.

Why does one instance work but several struggle?

Shared bandwidth, encoding resources or devices may be limiting concurrency. Add instances gradually to find the bottleneck.

Content reviewed: September 6, 2026 · Xiaolu Assistant product team

KEEP EXPLORING

Keep exploring

READY WHEN YOU ARE

Your next live starts here.

Find plans, licenses and guides in the user center.

Sign up and get started