Fix connection and network errors

If Flow shows Connection lost or cannot reach its servers, check the connection before changing app settings. A VPN, proxy, firewall, filtering service, or service interruption can affect Flow even when some websites still load.

Find where the connection fails

1. Open a website. If other apps are offline too, restore the device's connection first.
2. Check any Flow service banner. Use View status if one appears. See service status alerts.
3. Quit and reopen Flow, then test a short phrase.
4. Compare the network configuration. If you control a VPN or filtering tool, temporarily test without it, then restore it. On a managed device or network, ask IT to make the comparison.

A successful test without a tool helps identify where to configure access; it does not require leaving protection off.

Mac and Windows: check proxies and security tools

Quit Flow before changing proxy settings. On Mac, open System Settings → Network; on Windows, Settings → Network & internet → Proxy. Check any active proxy with your administrator, then reopen Flow and compare the result.

If an approved temporary test shows a firewall or security tool is involved, add the Wispr Flow application to its allowed-app configuration and test again with the tool enabled.

Use the full network guide for permanent rules: Configure your network for Wispr Flow separates website/download domains, dictation endpoints, TLS inspection, and organization IP restrictions. A short list of website domains is not a complete deny-by-default firewall policy.

Flow uses system proxy settings and trusted organizational certificates. IT may need to install the proxy root certificate in the operating system's trust store. TLS inspection can still force slower fallback connections; the network guide explains the targeted inspection bypass.

If DNS filtering is suspected, compare with a DNS server approved for your network, restart Flow, and retest. Do not change a managed network's configuration without involving its administrator.

iPhone and Android

Platform	Connection checks
iPhone	Check the active VPN in Settings and any filtering app. For Wi-Fi proxy settings, open Settings → Wi-Fi → network info → HTTP Proxy. Compare the connection after any approved change.
Android	Check Settings → Network & internet → VPN. Inspect the current network's advanced proxy settings and any firewall or filtering app. Settings names can vary by device.

Restore the required VPN, proxy, or filtering configuration after testing. If a corporate connection is required, ask IT to allow Flow using the network guide rather than leaving it disabled.

If the Android bubble is missing or unresponsive

That can be an Accessibility or background-operation issue rather than lost internet:

• Warning icon: follow the prompt to re-grant Accessibility access.
• Restart/retry icon: use it to reconnect the service or open Flow for recovery.
• Reconnecting bubble: wait for reconnection; this state is not tappable.

After a reboot or update, Flow requires Accessibility to remain enabled and onboarding to be complete. Open the app once if the bubble does not return. For battery optimization, autostart, and manufacturer-specific restrictions, follow Android setup.

Chrome extension

If the extension shows No Internet Connection, close and reopen its popup. Check Chrome Settings → System → Open your computer's proxy settings. If your organization configured the proxy, contact its administrator; compare any VPN or filtering configuration using the same approach above.

Recover after a dropped connection

Reconnect, then check History on the device where you dictated. Saved audio may be retryable; deleted or uncaptured audio is not. Desktop retention policies can disable this recovery. Use Retry failed transcriptions for the applicable controls.

On Android, starting dictation is blocked offline. A Paste action uses text already captured on the clipboard; a transcription Retry needs a working connection. Slow transcription with saved audio is covered in slow or failed transcription.

Sign-in errors and persistent failures

Couldn't reach Wispr Flow calls for the connection checks above. For Too many requests, wait before trying again. For an organization network restriction, switch to an approved network or contact your administrator.

If corporate SSO repeatedly signs you out, ask IT to review the proxy certificate and allowed endpoints. Contact support with your OS, Flow version, exact error, security/network tools, and which comparison changed the result.