Troubleshoot connection and voice

Separate endpoint access from workspace media. First prove the agent is ready and the page is reachable, then test microphone, transcription, model response, and speech output in that order.

Public UI does not open

Confirm the card says ready and use the exact HTTPS link. Check that your current public IP is in the agent’s allowlist. VPN, office, mobile, and home addresses can differ from the address detected at launch.

Open Settings, add the current IP, save, and retry. Do not widen the rule to the whole internet as a diagnostic shortcut.

Tailnet UI does not open

Confirm the device running the browser is signed into the intended tailnet. Wait for the agent card to report tailnet DNS and HTTPS readiness. Check MagicDNS, ACL or grants policy, accepted DNS, and the agent tag.

Test the MagicDNS name rather than substituting a public IP.

Workspace does not connect

Reload once after the Cloud card is ready. A connection error affecting every browser can indicate a runtime transport issue. A problem affecting one browser can involve cached state, permissions, or network restrictions.

Microphone input fails

Allow microphone access for the exact agent origin. Confirm the correct input device, then test push-to-talk before wake mode. Close other applications holding exclusive microphone access.

Transcription fails

If transcription uses Voice Studio, verify the configured private address and service health. If it uses the default path, confirm audio reaches the workspace and speech is long and clear enough to transcribe.

Speech output fails

Confirm Speech Output is enabled, the selected provider/model mode matches the chosen engine, and a valid voice is selected. Native audio providers ignore local Voice Studio settings.

For Voice Studio, preview the source sample inside Voice Studio. If the preview fails there, fix the profile or service before testing chat playback.

Feedback or duplicate speech

Use headphones, lower speaker volume, enable echo cancellation, and shorten the wake follow-up window. Test in push-to-talk mode to determine whether wake listening is reactivating on the assistant’s own audio.