ErrorAway
Home  ›  Discord  ›  Authorization flow cancelled

Discord "Authorization flow cancelled because your browser window was closed"? 7 fixes

✓ Reviewed & updated July 2026

By the ErrorAway Team · Hands-on tested on Windows 10 & 11

You're connecting a game, a bot, a Stream Deck plugin, or logging in to a website with Discord. A Discord authorization window opens, you click Authorize — and instead of connecting, you get "Authorization flow cancelled because your browser window was closed." Confusing, because you didn't close anything. In reality, something on your system closed or blocked that window before Discord could finish the handshake — and it's almost always a popup blocker, an extension, or the wrong browser opening the link.

Work through these in order. The first three fix most cases.

Quick checklist

  1. Retry and let the whole flow finish
  2. Turn off popup blockers for Discord
  3. Disable ad-block/privacy extensions or use incognito
  4. Sign in to discord.com in your browser first
  5. Check your default browser
  6. Clear the browser's Discord cookies
  7. Restart and update Discord (and check its status)

Quick safety note: only authorize apps you trust. The authorization screen lists exactly what the app can access — if a random bot asks for more than it needs, cancel on purpose.

Why this error happens

Discord's "connect" process works like a relay: the app opens a Discord window in your browser, you approve, and the browser hands a code back to the app. If that window gets blocked, closed early, or opened in the wrong browser, the relay breaks and Discord reports the flow as cancelled. The usual culprits are popup blockers, ad-block or privacy extensions, stale Discord cookies, or a default-browser mix-up.

The 7 fixes

1

Retry — and let the whole flow finish

Sometimes the fix really is patience: the window must stay open until you land back on a "success" or redirect page.

  • Start the authorization again from the app or website.
  • Click Authorize and don't close, minimise, or switch away until it completes on its own.
2

Turn off popup blockers for Discord

The most common cause — the browser silently kills the auth popup, and Discord reads that as "window closed."

  • In Chrome/Edge: Settings → Privacy → Site settings → Pop-ups and redirects → add discord.com to the Allowed list.
  • If the address bar shows a "popup blocked" icon during the flow, click it and choose Always allow.
3

Disable ad-block/privacy extensions — or use incognito

Ad blockers and privacy extensions often block the redirect that completes the handshake.

  • Fastest test: open an incognito/private window (extensions are off there by default), log in to discord.com, and run the authorization again.
  • If it works there, an extension was the culprit — whitelist discord.com in it, or keep authorizations in incognito.
4

Sign in to discord.com in your browser first

If the auth window also has to handle a full login, there's more to go wrong. Pre-logging in shortens the flow to a single Authorize click.

  • Open discord.com/login in your normal browser and sign in.
  • Now retry the authorization from the app — it should skip straight to the Authorize screen.
5

Check your default browser

Apps open the auth window in your system's default browser. If that's set to a browser you never use (or an in-app browser), the flow can open where you can't see or finish it.

  • Go to Settings → Apps → Default apps and set your main browser (Chrome, Edge, Firefox) as default.
  • Retry the authorization.
6

Clear the browser's Discord cookies

A stale or corrupted Discord session cookie can break the handshake mid-flow.

  • In your browser, press Ctrl + Shift + Del, choose Cookies and other site data (you can limit the range to recent), and clear.
  • Sign back in to discord.com (fix 4) and retry.
7

Restart and update Discord — and check its status

If the flow starts from the Discord desktop app, a stale app session can cancel it from that side.

  • Press Ctrl + Shift + Esc, end every Discord task, and reopen it (it updates itself on launch).
  • Still failing everywhere? Check discordstatus.com — during an API incident, authorizations fail for everyone and the only fix is waiting.

Frequently asked questions

I never closed the window. Why does Discord say I did?

Because something closed it for you — usually a popup blocker or extension killing the window/redirect. To Discord, a blocked window and a closed window look identical. Fixes 2 and 3 target exactly this.

It happens when connecting a specific app (game, Stream Deck, bot). Is that app broken?

Usually not — the browser side of the handshake is failing, and the same fixes apply. If every other authorization works and only one app consistently fails after fixes 1-6, then contact that app's support, since its redirect setup may be misconfigured.

Is authorizing apps through Discord safe?

The mechanism itself is safe — it's Discord's official way to grant limited access without sharing your password. Just read the permissions list on the Authorize screen and only approve apps you trust. You can review and remove connections anytime in Discord's Settings → Authorized Apps.

Does this happen on phones too?

Yes — most often when the link opens in an "in-app browser" inside another app. Copy the link into your real browser (Chrome/Safari), or set your default browser properly, and the flow completes normally.

More Discord trouble? See: Discord won't open · Error 3004 when screen sharing · Stuck on "Update Failed". Still stuck? Send us the details.

Send us the details →