doctl auth init freezes after OK on Windows
Fixes doctl auth init freezing after printing OK on Windows. Use this when the interactive init accepts the token but never returns to the prompt. Not for auth rejections or non-Windows installs.
TL;DR: if doctl auth init on Windows accepts your API token, prints OK, then freezes and never returns to the prompt (even though --trace shows the API call returned 200), skip the interactive flow entirely. Create the config file yourself at %APPDATA%\doctl\config.yaml with just the access-token entry, then run doctl normally. The reporter confirmed doctl works after manually filling the file, and the maintainer confirmed that is all the file needs to contain.
Steps
- Create
%APPDATA%\doctl\config.yamlcontaining only the access-token entry for your token.
- Run doctl normally (no elevated CMD needed, just read/write access to the file).
Expected: commands authenticate. Success check: a simple doctl account get works.
When to use this
- doctl 1.48.1 on Windows 10, auth init freezes post-OK.
When NOT to use this
- Auth is rejected; check the token.
- Non-Windows; the interactive flow works there.
Compatibility
- doctl 1.48.1 on Windows (thread closed 2020; the workaround stands).
Variant phrasings
- "doctl auth init hangs windows"
- "doctl freezes after OK"
Root cause
The interactive init flow hung on Windows after the token validated, never completing its final steps.
Edge cases
- You do not need an elevated CMD; plain read/write access to the config file is enough.
Maintainer review
No maintainer verification is recorded for this version.
This records the version a maintainer checked. It does not assert that the version is the latest upstream release.