Hi Blizzard team,
I’m reporting a critical issue with the Battle.net launcher that currently prevents me from logging in by any means.
After link my Xbox/Game Pass account the launcher continues to force an OAuth redirect to:
localhost:0/?ST=EU-[token]®ion=EU&accountName=[my-email]
This behavior is technically flawed for several reasons:
- Port
0is a reserved and invalid port. No HTTP server can bind to it. - The Battle.net client does not spawn any local listener/server, yet it still builds a redirect URL towards localhost.
- Any modern browser (Chrome, Edge, Firefox) instantly blocks the redirect with
ERR_UNSAFE_PORT. - This issue occurs even when trying to log in with standard email and password, without using Xbox or SSO flows.
- The bug persists across:
- Fresh OS installs
- VPN and location changes (EU tested: France, Germany, NL)
- Full credential and cache wipe (cmdkey, Windows Credential Manager, AppData, ProgramData, etc.)
- Simulated redirect with a local Python server (HTTP 200 OK returned correctly on port 12345)
- WebView2 runtime reset
No workaround has worked. The launcher refuses to complete the login flow because it expects a response on a port that cannot exist.
You are currently breaking your own product for legitimate users. The authentication flow is completely non-functional, and the launcher offers no fallback.
Please:
- Fix this redirect behavior immediately.
- Re-enable proper dynamic port allocation for local OAuth callbacks (as previously used).
- Provide a way to log in that doesn’t rely on localhost-based SSO at all.
It’s been almost a year since I last had the (mis)fortune of using one of your products. Yesterday, like a fool, I got tricked by a discounted offer. And now, here I am, stuck in this ridiculous situation.
But don’t worry — after the legal complaint I’m about to file due to your inability to provide access to a product I legally purchased, you’ll go back where you belong: forgotten.
Shame on you.
