Cloudflare Workers / Cloudflare

Cloudflare Wrangler login hangs indefinitely on OAuth callback rejection

Debug Cloudflare Wrangler CLI login command hanging when OAuth callback returns an error (not access_denied), waiting full 120s timeout instead of surfacing the actual OAuth error to the user Includes evidence for Cloudflare Workers troubleshooting demand.

Source-backed Last updated May 23, 2026 1 source Needs local verification

Category: Cloudflare
Error signature: wrangler login hangs until 120s OAuth timeout — OAuth provider redirect with error code not shown to user
Quick fix: Verify the account session, API key, provider settings, and environment where the failing tool is running.
Updated: May 23, 2026
Verification status: Source-backed
Evidence: 1 public source URL

Before you change production

This page includes public source URLs in the imported troubleshooting record. Compare those references with your version and environment before applying changes.

Reproduce the smallest failing action and save non-secret logs before changing configuration.
Check versions for Cloudflare Workers, related SDKs, package managers, CI runners, and hosting providers.
Change one setting or dependency at a time, then rerun the same failing command or request.
Avoid destructive commands, credential rotation, billing changes, or security relaxations without a rollback plan.

What this error means

wrangler login hangs until 120s OAuth timeout — OAuth provider redirect with error code not shown to user is a Cloudflare Workers failure pattern reported for developers trying to debug cloudflare wrangler cli login command hanging when oauth callback returns an error (not access_denied), waiting full 120s timeout instead of surfacing the actual oauth error to the user. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

Related GitHub PR #14022 in cloudflare/workers-sdk (opened May 23, 2026). When OAuth provider rejects the callback, Wrangler writes no HTTP response; server.close() blocks until connections end. Users see generic timeout, not the actual OAuth error_description (RFC 6749 §4.1.2.1). Affects every developer authenticating with Cloudflare.

Common causes

Related GitHub PR #14022 in cloudflare/workers-sdk (opened May 23, 2026). When OAuth provider rejects the callback, Wrangler writes no HTTP response; server.close() blocks until connections end. Users see generic timeout, not the actual OAuth error_description (RFC 6749 §4.1.2.1). Affects every developer authenticating with Cloudflare.

Quick fixes

Confirm the exact error signature matches wrangler login hangs until 120s OAuth timeout — OAuth provider redirect with error code not shown to user.
Check the Cloudflare Workers account, local tool state, and provider configuration involved in the failing workflow.
Verify the account session, API key, provider settings, and environment where the failing tool is running.

Platform/tool-specific checks

Verify the command, editor, extension, or API client that produced the error.
Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

Capture the exact error message and the command, editor action, or request that triggered it.
Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
Review the source evidence below and compare it with your environment.
Apply one change at a time and rerun the smallest failing action.
Keep the working fix documented for the team or deployment environment.

How to prevent it

Keep provider/tool configuration documented.
Record non-secret diagnostics such as tool version, provider name, model name, and command path.
Add a lightweight check before CI or production workflows depend on the tool.

Diagnostic flow for this page

Match wrangler login hangs until 120s OAuth timeout — OAuth provider redirect with error code not shown to user exactly before applying the quick fix.
Compare the failing environment with Cloudflare Workers versions, account scope, provider settings, and deployment context.
Check the listed common causes in order, starting with the cause that best matches your logs.
Use the evidence status below to decide whether to confirm against public sources or official documentation.
Apply one reversible change, rerun the smallest failing action, and keep rollback notes.

FAQ

What does wrangler login hangs until 120s OAuth timeout — OAuth provider redirect with error code not shown to user mean in Cloudflare Workers?

wrangler login hangs until 120s OAuth timeout — OAuth provider redirect with error code not shown to user indicates the workflow described by "Cloudflare Wrangler login hangs indefinitely on OAuth callback rejection" failed in a Cloudflare context. Start by confirming the exact signature and the component that emitted it.

What should I check first for wrangler login hangs until 120s OAuth timeout — OAuth provider redirect with error code not shown to user?

Check whether this cause matches your environment: Related GitHub PR #14022 in cloudflare/workers-sdk (opened May 23, 2026). When OAuth provider rejects the callback, Wrangler writes no HTTP response; server.close() blocks until connections end. Users see generic timeout, not the actual OAuth error_description (RFC 6749 §4.1.2.1). Affects every developer authenticating with Cloudflare.

Is the wrangler login hangs until 120s OAuth timeout — OAuth provider redirect with error code not shown to user guidance source-backed?

The "Cloudflare Wrangler login hangs indefinitely on OAuth callback rejection" page is labeled source-backed. It has 1 public source URL from github.com, so use that evidence status when deciding how much additional verification you need.

When should I avoid the quick fix for wrangler login hangs until 120s OAuth timeout — OAuth provider redirect with error code not shown to user?

For "Cloudflare Wrangler login hangs indefinitely on OAuth callback rejection", avoid applying "Verify the account session, API key, provider settings, and environment where the failing tool is running." when the error text differs, the affected version or provider is different, or the change would touch credentials, billing, DNS, production deploy settings, or irreversible data.

What should I collect before debugging wrangler login hangs until 120s OAuth timeout — OAuth provider redirect with error code not shown to user?

For "Cloudflare Wrangler login hangs indefinitely on OAuth callback rejection", collect the failing Cloudflare Workers command or request, non-secret configuration, versions, timestamps, request IDs when available, and the smallest reproduction that still triggers the signature.