Wispr Flow website loads but sign-in and downloads fail in one browser

Last updated: September 12, 2026

Available on: Mac, Windows

If the Wispr Flow homepage loads but the download page, sign-in page, or Help Center hangs or comes up blank — and works fine in another browser or on your phone — the cause is usually a browser setting. Most cases resolve in under 5 minutes.

Quick checks

  • Is there an active incident? Check the Wispr Flow status page. The absence of an in-app notice does not rule out an incident.

  • Does another browser work? Open the same page in a different browser on the same computer. If it loads there, the problem is limited to the first browser.

  • Does your phone load the site? Open the site on a phone or tablet on the same Wi-Fi. If it loads there but not on your computer, the problem is on that computer or browser — continue below.

Why this happens

Browsers can run their own lookups using DNS over HTTPS, also shown as Secure DNS. That lookup works independently of your operating system and router, so a browser can resolve addresses differently from the rest of your computer.

When the browser resolves the main domain but fails on the supporting addresses a page needs, the homepage loads while everything else breaks. The browser reports this as a cross-origin or blocked-resource error, which looks like a website fault but is a name-resolution failure inside the browser.

Each browser keeps its own DNS over HTTPS setting, so the site can work in Chrome and still fail in Firefox on the same machine.

Sign-in: Flow's sign-in opens your default browser to wisprflow.ai/login and waits for it to complete, so a working browser page is required. Finish the flow in the browser while Flow is running; on success Flow brings itself to the front. If a link is stale, click Sign In again to start over. If your credentials come back invalid, you'll see a generic "Failed sign-in" notification with no specific reason.

Corporate networks: TLS/SSL inspection can break the app's secure connection to Wispr Flow even when basic connectivity looks fine. Ask your network or security team for an inspection bypass for the Wispr Flow domains, applied to the affected user or group.

How to fix this

Step 1: Adjust your browser's DNS setting

Apply this in each browser where the site fails. Either turn the setting off so the browser follows your system and router DNS, or leave it on and pick a mainstream provider.

Chrome and Edge

  1. Open Settings → Privacy and security → Security.

  2. Scroll to the Use secure DNS row.

  3. Switch it off, or leave it on and select a mainstream provider such as Cloudflare or Google.

  4. Quit the browser completely, reopen it, and load the page again.

If the failing page loads, you're done. If not, go to Step 2.

Firefox

  1. Open Settings → Privacy & Security.

  2. Scroll to the DNS over HTTPS section.

  3. Select Off, or keep it enabled and choose a mainstream provider such as Cloudflare.

  4. Quit Firefox completely, reopen it, and load the page again.

If the failing page loads, you're done. If not, go to Step 2.

Safari

Safari has no DNS over HTTPS setting of its own — it follows macOS.

  1. Open System Settings → Network and review the DNS settings for your active connection.

  2. Check for a configuration profile or content-filtering app overriding DNS for the whole system.

  3. Reload the page in Safari.

If the failing page loads, you're done. If not, go to Step 2.

Step 2: Rule out extensions, security software, and VPNs

  1. Open the site in a private or incognito window, where extensions are disabled. If it loads, re-enable your extensions one at a time to find the one interfering.

  2. Pause antivirus, endpoint-protection, or web-filtering software, then reload. These tools often filter subdomains while allowing the main domain.

  3. Disconnect from any VPN or proxy, then reload — they can change name resolution or intercept HTTPS. If you must stay connected, ask your IT team to exclude the domains below from proxying and TLS/SSL inspection.

  4. Check your hosts file for stale entries pointing at Wispr Flow domains, and remove them.

Domains to allow

If you or your IT team maintain an allowlist, allow these over HTTPS on port 443:

  • wisprflow.ai (website and sign-in)

  • *.wisprflow.ai

  • *.wisprflow.com

Allow the full wildcard rather than pinning single hostnames. If your network uses TLS/SSL inspection, request an inspection bypass for these domains, not just DNS access.

How to install or update Flow while the site is blocked

You do not need the website working to install or update Flow.

Update a copy you already have

  1. Right-click the Wispr Flow icon in your Windows system tray or Mac menu bar.

  2. Select Check for updates… at the top of the menu. Flow downloads the latest build without using a browser, even when the download page will not load.

If both the in-app update and the direct links below fail, the block is at the network level, not in the browser.

Download a fresh installer

These direct links bypass the download page:

Note: Do not copy an installer from another computer — you get whatever version that machine had, which may be many builds behind. Update through the app or a direct link instead.

FAQs

My router already uses Cloudflare DNS. Why would the browser matter?

A browser using DNS over HTTPS bypasses your router and sends lookups to its own resolver, so the browser setting has to be changed separately.

Is a cross-origin error in the console a bug on Wispr Flow's side?

Usually not. When part of a page never loads because its address failed to resolve, the browser often reports a cross-origin or blocked-resource error. If the site loads on another device on the same network, the cause is local.

It fails on two computers at once. Doesn't that mean it's your servers?

Not necessarily. Computers sharing an operating system version, browser defaults, or security software share the same DNS behavior, so they can fail together for the same local reason.

Was my account locked or restricted?

No — a DNS or browser problem does not affect your account, subscription, dictionary, or history. If your organization restricts Flow to approved networks, contact your IT team.

Can I sign in on Android without a browser installed?

No. Android sign-in requires an installed browser; without one, sign-in cannot start.

Still stuck?

Contact support and include the following so we can pinpoint which address is blocked:

  • The full URL of the page that fails and the exact error text in your browser console

  • Your platform, browser, and browser version

  • Which steps you already tried, and whether the site loads on your phone on the same network

Most cases like this are resolved in one reply.

If the website is unreachable, reach support from inside the app: on desktop, the tray menu or Help → "Talk to Support" (Cmd+/ on Mac); on iOS, Menu → "Talk to Support"; on Android, drawer → "Report an issue". You will receive an automatic "Submission Received" confirmation email with Help Center and Status Page links.