When I try to login or run a command, I get this:
Doppler Error: Get "https://api.doppler.com/v3/configs/config/secrets/download?config=dev&format=json&project=api": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
It was working earlier today across all my projects.
Hey dangerous and welcome to the Doppler community!
Is there anything that changed between now and earlier network wise? For example, phone tethering vs. WiFi, or changing WiFi networks?
Also, are you experiencing this issue locally or in a live environment?
Cheers,
Ryan
I’m on my home wifi and it is happening locally. We are not running doppler on prod yet.
Ok, strange. We’ll figure this out!
Would you be able to try either connecting to a different WiFi endpoint on your router (if that’s possible) or try using your phone as a hotspot and seeing if the issue persists?
Also, what model and brand is your Wifi router?
Finally, are you using any debugging proxies such as Charles that could be interfering with network connections?
It worked during the day today while our team was working. But now that I try to run it again at 11pm, it is returning:
Doppler Error: Get "https://api.doppler.com/v3/configs/config/secrets/download?config=dev&format=json&project=airflow": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Ok, not sure yet what the cause is.
What model and brand is your Wifi router, and who is your ISP?
And is this issue still happening?
Just wanted to check in to see if you’re still experiencing this issue?
Everything is working as usual now. Thank you.
Just got the error again:
Doppler Error: Get "https://api.doppler.com/v3/configs/config/secrets/download?config=dev_dangerous&format=json&project=api": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Sorry you keep running into this again.
Can you provide the exact command you’re running, as well as adding the --debug flag which may provide an insight into what is happening.
Also, are you using a VPN or other proxy?
I’m currently experiencing this issue.
I noticed that whenever I turned on my VPN, doppler CLI is about to pull credentials. But it exceeds the deadline whenever I try it on my local network.
Is there some sort of location restriction?
Hi @tnkemdilim and welcome to the Doppler community!
Sorry you’re running into this issue.
Could you please try running the command with the --no-dns-resolver and --debug flags?
I was having the same problem but running the command with --no-dns-resolver seems to work for now 
I am running into the same issue on an EC2 machine in AWS. The --no-dns-resolver flag worked for me also. Is there a way to configure doppler to use OS DNS settings by default?
Debug: Checking for latest version of the CLI
Debug: Using custom DNS resolver 1.1.1.1:53
Debug: Get "https://api.github.com/repos/DopplerHQ/cli/releases/latest": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Debug: Get "https://api.github.com/repos/DopplerHQ/cli/releases/latest": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
I would also like to configure mine to work like this because I’m running into the same issue
HI @kirill and welcome to the Doppler community!
Our engineers are working on a fix but in the meantime, you can disable the DNS resolver for all requests by setting the following environment variable:
export DOPPLER_DISABLE_DNS_RESOLVER="true"
Hi @kirill and @David_Kinuthia,
Wanted to let you know that we’ve just released CLI version v3.31.0 which disables our custom DNS resolver by default, meaning the --no-dns-resolver flag or DOPPLER_DISABLE_DNS_RESOLVER environment variable is no longer necessary.
HI @tnkemdilim and welcome to the Doppler community!
Your timeout issues may have been caused by our custom DNS resolver which is now disabled by default as of release v3.31.0.
Could you try updating the CLI by running doppler update and let me know if it now works for you when using your VPN?
I normally encounter this issue as well. I’m currently using Windows WSL2. Running doppler is slow or sometimes timeout with the same error above,
