Priority Sign In callback fails — launcher never binds the callback port
Posted: Fri Oct 09, 2026 12:27 pm
Launcher v1.4.1, Windows 11.
After signing in on the website, the browser is redirected to https://127.0.0.1/callback?code=...&st=... and fails with “unable to connect”.
What I’ve ruled out:
Not a browser issue: fails identically in Firefox and Edge.
Not HTTPS upgrading: Firefox HTTPS-Only Mode is disabled, so the launcher itself emits https://.
Not permissions: launcher run as administrator, same result.
Not a VPN: tested with VPN off.
Nothing is listening: netstat -ano | findstr LISTENING | findstr :80 returns nothing while the callback page is open.
After signing in on the website, the browser is redirected to https://127.0.0.1/callback?code=...&st=... and fails with “unable to connect”.
What I’ve ruled out:
Not a browser issue: fails identically in Firefox and Edge.
Not HTTPS upgrading: Firefox HTTPS-Only Mode is disabled, so the launcher itself emits https://.
Not permissions: launcher run as administrator, same result.
Not a VPN: tested with VPN off.
Nothing is listening: netstat -ano | findstr LISTENING | findstr :80 returns nothing while the callback page is open.