Troubleshoot Desktop Startup, Audio, and Local Sidecar Problems

Diagnose app launch, deep link, microphone, forallcli health, local WebSocket, and model failures.

Written By 4ALL.LIVE

Last updated 12 days ago

Isolate desktop-specific failures and collect a redacted evidence package without deleting local state prematurely.

Best for: Operators, production IT, and 4All support.

Before you start

Included with the desktop application; support escalation may require device/license context.

  • Use a non-production event for commissioning.
  • Record the current build and workstation owner.
  • Prepare a documented fallback before making changes.
  • Record workstation, OS, build, user role, event, time, and first error.
  • Stop production before restarting app/sidecar.
  • Keep tokens and private event content out of evidence.

Troubleshooting steps

  1. Classify the failure: app launch, update, browser authorization/deep link, workspace API, microphone permission/device, sidecar health, model load, or realtime WebSocket.
  2. Confirm system time, storage, network, and endpoint-security status.
  3. For authorization, test web sign-in and registered deep-link return.
  4. For audio, verify OS permission, stable device UID, channel, sample rate, and exclusive-use conflicts.
  5. For local STT, initialize forallcli, test http://127.0.0.1:8787/health, enumerate /api/audio/devices, and connect ws://127.0.0.1:8787/ws/realtime.
  6. Try localhost if 127.0.0.1 binding differs.
  7. Collect app/updater/sidecar logs, exact error, resource status, and a minimal reproduction.
  8. Use an approved cloud-STT fallback when policy/plan permit, then escalate with redacted evidence.

After the fix: The problem is isolated to a specific desktop layer or a tested fallback restores service.

Confirm the fix

  • First error captured before restarts.
  • Audio test uses intended device/channel.
  • Sidecar and WebSocket status are explicit.
  • No token or transcript content is exposed.

If the problem continues

  • Port 8787 busy/blocked: identify the approved local process and security rule.
  • Sidecar starts but no devices: regrant microphone access and reconnect hardware.
  • WebSocket error: confirm health first, then local firewall/binding.
  • Update regression: follow controlled rollback; do not erase application data.

Escalation and safety

Important: Do not share desktop tokens, authorization codes, raw private transcripts, or unredacted logs. Do not delete caches/configuration until support confirms the recovery impact.