#10603 Cloudflare OAuth provider does not accept redirect_url where the --callback-host is set to 0.0.0.0
Fixed in PR #9396 (merged 2026-01-20), released in wrangler 4.59.3. OAuth redirect_uri now always uses localhost:8976 as required by Cloudflare.
Close with comment explaining fix is available in wrangler 4.59.3+
Analysis Report
Issue Review: cloudflare/workers-sdk#10603
Summary
Cloudflare OAuth does not accept 0.0.0.0 as redirect_uri when using --callback-host=0.0.0.0 for Docker workflows.
Findings
- Created: 2025-09-10
- Updated: 2025-10-07
- Version: wrangler 4.35.0 → 4.60.0 (current)
- Component: wrangler (login/OAuth)
- Labels: bug
- Comments: 0
Key Evidence
- PR #9396 merged on 2026-01-20 explicitly fixes this issue
- PR title: "Always pass a valid
redirect_uricallback parameter (localhost:8976) to Cloudflare OAuth API, even when the--callback-hostand--callback-portparams would not be accepted" - Fix released in wrangler 4.59.3 per CHANGELOG.md
- The fix ensures the
redirect_uriis always set tolocalhost:8976(which Cloudflare OAuth requires), while still allowing users to configure the actual listening host/port for container scenarios - The changelog entry provides a detailed example of the correct Docker workflow
Recommendation
Status: CLOSE
Reasoning: The issue has been fixed in PR #9396, which was merged on 2026-01-20 and released in wrangler 4.59.3. The fix correctly addresses the root cause by always sending localhost:8976 as the redirect_uri to Cloudflare OAuth, while allowing the Wrangler OAuth server to listen on a different host/port (e.g., 0.0.0.0). Users can now run Wrangler in containers without the workaround.
Action: Close the issue with a comment explaining the fix.
Suggested Comment
This issue has been fixed in PR #9396, released in wrangler 4.59.3.
The fix ensures the
redirect_uriis always set tolocalhost:8976(which Cloudflare OAuth requires), while you can still configure--callback-hostand--callback-portfor the Wrangler OAuth server to listen on a different address (useful for container scenarios).Please upgrade to wrangler 4.59.3 or later. If you still experience issues after upgrading, please let us know and we can reopen this issue.
Notes & Feedback (0)
No notes yet.