Immutable solution version
doppler login failing with EOF errors on a new Mac: check your network filter
Complete solution
If doppler login fails almost immediately with EOF errors on api.doppler.com but your network otherwise works, run this sanity check first: curl -v 'https://api.doppler.com/v3/projects'. If that looks healthy, the problem is almost certainly something intercepting your traffic locally, like a corporate network filter or proxy, which is exactly what caused this issue.
When it applies
Not specified by the original author.
Instructions
If doppler login fails almost immediately with EOF errors on api.doppler.com but your network otherwise works, run this sanity check first: curl -v 'https://api.doppler.com/v3/projects'. If that looks healthy, the problem is almost certainly something intercepting your traffic locally, like a corporate network filter or proxy, which is exactly what caused this issue. The CLI polls /v3/auth/cli/authorize every 2 seconds while you complete the browser step, and a filter that kills repeated connections produces these EOFs. As a workaround while you sort the network, grab a personal token from the dashboard (Tokens, Personal tab) and load it with pbpaste | doppler configure set token. That bypasses the browser polling entirely.
Source: gh:DopplerHQ/cli#362 (Doppler)
Evidence
In gh:DopplerHQ/cli#362, the issue was: A fresh brew install on an M1 Mac failed doppler login with repeated "Post https://api.doppler.com/v3/auth/cli/authorize: EOF" errors, plus the same EOF on the analytics POST. The maintainer walked through diagnostics: direct curls to the API worked fine, so the API was healthy, and the reporter could not make even curl fail when run every two seconds. The workaround offered was a personal token via pbpaste | doppler configure set token. In the end the reporter found the cause: a buggy network filter installed by their company. The maintainer confirmed the diagnosis.. The verified answer: If doppler login fails almost immediately with EOF errors on api.doppler.com but your network otherwise works, run this sanity check first: curl -v 'https://api.doppler.com/v3/projects'. If that looks healthy, the problem is almost certainly something intercepting your traffic locally, like a corporate network filter or proxy, which is exactly what caused this issue. The CLI polls /v3/auth/cli/authorize every 2 seconds while you complete the browser step, and a filter that kills repeated connections produces these EOFs.. Issue URL: https://github.com/DopplerHQ/cli/issues/362
By @issueatlas · Version 1 · Exact version
Maintainer review
Checking maintainer review for this exact version…
A maintainer review records the library version checked. It does not assert that it is the latest upstream release. Reported outcomes are separate evidence.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_jIUMDocET0l2gCXcpQ116A" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">doppler login failing with EOF errors on a new Mac: check your network filter <span>— Vectle</span></a>