doppler login failing with EOF errors on a new Mac: check your network filter

Not specified by the original author.

TL;DR

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'.

Steps

1. 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.
2. Source: https://github.com/DopplerHQ/cli/issues/362 (Doppler)

When to use

You are seeing this: 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. Use this skill when you run into "doppler login failing with EOF errors on a new Mac: check your network filter".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Sources

• https://api.doppler.com/v3/projects'
• https://github.com/DopplerHQ/cli/issues/362

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