# Anyone having problems fetching secrets due to context deadline exceeded? **URL:** \ **Category:** Need Help\ **Created:** [February 5, 2021, 3:39am UTC](https://community.doppler.com/t/anyone-having-problems-fetching-secrets-due-to-context-deadline-exceeded/98 "2021-02-05T03:39:37Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![dangerous](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/dangerous/32/56_2.png) [@dangerous](https://community.doppler.com/u/dangerous)\ **Post date:** [February 5, 2021, 3:39am UTC](https://community.doppler.com/t/anyone-having-problems-fetching-secrets-due-to-context-deadline-exceeded/98/1 "2021-02-05T03:39:37Z")
When I try to login or run a command, I get this: ```auto 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. ---
**Author:** ![ryan-blunden](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/ryan-blunden/32/9_2.png) [@ryan-blunden](https://community.doppler.com/u/ryan-blunden)\ **Post date:** [February 5, 2021, 4:08am UTC](https://community.doppler.com/t/anyone-having-problems-fetching-secrets-due-to-context-deadline-exceeded/98/2 "2021-02-05T04:08:37Z")
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 ---
**Author:** ![dangerous](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/dangerous/32/56_2.png) [@dangerous](https://community.doppler.com/u/dangerous)\ **Post date:** [February 5, 2021, 4:29am UTC](https://community.doppler.com/t/anyone-having-problems-fetching-secrets-due-to-context-deadline-exceeded/98/3 "2021-02-05T04:29:18Z")
I’m on my home wifi and it is happening locally. We are not running doppler on prod yet. ---
**Author:** ![ryan-blunden](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/ryan-blunden/32/9_2.png) [@ryan-blunden](https://community.doppler.com/u/ryan-blunden)\ **Post date:** [February 5, 2021, 4:44am UTC](https://community.doppler.com/t/anyone-having-problems-fetching-secrets-due-to-context-deadline-exceeded/98/4 "2021-02-05T04:44:08Z")
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? ---
**Author:** ![dangerous](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/dangerous/32/56_2.png) [@dangerous](https://community.doppler.com/u/dangerous)\ **Post date:** [February 6, 2021, 7:40am UTC](https://community.doppler.com/t/anyone-having-problems-fetching-secrets-due-to-context-deadline-exceeded/98/5 "2021-02-06T07:40:30Z")
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: ```auto 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) ``` ---
**Author:** ![ryan-blunden](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/ryan-blunden/32/9_2.png) [@ryan-blunden](https://community.doppler.com/u/ryan-blunden)\ **Post date:** [February 8, 2021, 4:03am UTC](https://community.doppler.com/t/anyone-having-problems-fetching-secrets-due-to-context-deadline-exceeded/98/6 "2021-02-08T04:03:03Z")
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? ---
**Author:** ![ryan-blunden](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/ryan-blunden/32/9_2.png) [@ryan-blunden](https://community.doppler.com/u/ryan-blunden)\ **Post date:** [February 12, 2021, 12:48am UTC](https://community.doppler.com/t/anyone-having-problems-fetching-secrets-due-to-context-deadline-exceeded/98/8 "2021-02-12T00:48:43Z")
Just wanted to check in to see if you’re still experiencing this issue? ---
**Author:** ![dangerous](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/dangerous/32/56_2.png) [@dangerous](https://community.doppler.com/u/dangerous)\ **Post date:** [February 12, 2021, 1:17am UTC](https://community.doppler.com/t/anyone-having-problems-fetching-secrets-due-to-context-deadline-exceeded/98/9 "2021-02-12T01:17:09Z")
Everything is working as usual now. Thank you. ![Sent from Front](https://us1.discourse-cdn.com/flex016/uploads/doppler/original/1X/b80b11203d97fe01c5597ca3be70406ea48f5709.gif) ---
**Author:** ![dangerous](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/dangerous/32/56_2.png) [@dangerous](https://community.doppler.com/u/dangerous)\ **Post date:** [February 12, 2021, 8:33pm UTC](https://community.doppler.com/t/anyone-having-problems-fetching-secrets-due-to-context-deadline-exceeded/98/10 "2021-02-12T20:33:53Z")
Just got the error again: ```auto 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) ``` ---
**Author:** ![ryan-blunden](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/ryan-blunden/32/9_2.png) [@ryan-blunden](https://community.doppler.com/u/ryan-blunden)\ **Post date:** [February 16, 2021, 10:07pm UTC](https://community.doppler.com/t/anyone-having-problems-fetching-secrets-due-to-context-deadline-exceeded/98/11 "2021-02-16T22:07:39Z")
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? ---
**Author:** ![tnkemdilim](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/tnkemdilim/32/172_2.png) [@tnkemdilim](https://community.doppler.com/u/tnkemdilim)\ **Post date:** [July 10, 2021, 11:03pm UTC](https://community.doppler.com/t/anyone-having-problems-fetching-secrets-due-to-context-deadline-exceeded/98/12 "2021-07-10T23:03:59Z")
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? ---
**Author:** ![ryan-blunden](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/ryan-blunden/32/9_2.png) [@ryan-blunden](https://community.doppler.com/u/ryan-blunden)\ **Post date:** [July 11, 2021, 6:28am UTC](https://community.doppler.com/t/anyone-having-problems-fetching-secrets-due-to-context-deadline-exceeded/98/13 "2021-07-11T06:28:05Z")
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? ---
**Author:** ![David\_Kinuthia](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/david_kinuthia/32/175_2.png) [@David\_Kinuthia](https://community.doppler.com/u/David_Kinuthia)\ **Post date:** [July 16, 2021, 8:59am UTC](https://community.doppler.com/t/anyone-having-problems-fetching-secrets-due-to-context-deadline-exceeded/98/14 "2021-07-16T08:59:51Z")
> [@ryan-blunden](#): > > –no-dns-resolver I was having the same problem but running the command with `--no-dns-resolver` seems to work for now 🙏 ---
**Author:** ![kirill](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/kirill/32/176_2.png) [@kirill](https://community.doppler.com/u/kirill)\ **Post date:** [July 17, 2021, 12:23am UTC](https://community.doppler.com/t/anyone-having-problems-fetching-secrets-due-to-context-deadline-exceeded/98/15 "2021-07-17T00:23:36Z")
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? ```auto 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) ``` ---
**Author:** ![lotap](https://avatars.discourse-cdn.com/v4/letter/l/7ea924/32.png) [@lotap](https://community.doppler.com/u/lotap)\ **Post date:** [July 19, 2021, 5:25pm UTC](https://community.doppler.com/t/anyone-having-problems-fetching-secrets-due-to-context-deadline-exceeded/98/16 "2021-07-19T17:25:35Z")
I would also like to configure mine to work like this because I’m running into the same issue ---
**Author:** ![ryan-blunden](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/ryan-blunden/32/9_2.png) [@ryan-blunden](https://community.doppler.com/u/ryan-blunden)\ **Post date:** [July 19, 2021, 9:43pm UTC](https://community.doppler.com/t/anyone-having-problems-fetching-secrets-due-to-context-deadline-exceeded/98/17 "2021-07-19T21:43:20Z")
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: ```auto export DOPPLER_DISABLE_DNS_RESOLVER="true" ``` ---
**Author:** ![kirill](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/kirill/32/176_2.png) [@kirill](https://community.doppler.com/u/kirill)\ **Post date:** [July 20, 2021, 3:19am UTC](https://community.doppler.com/t/anyone-having-problems-fetching-secrets-due-to-context-deadline-exceeded/98/18 "2021-07-20T03:19:53Z")
Thanks @ryan-blunden! That works. ---
**Author:** ![ryan-blunden](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/ryan-blunden/32/9_2.png) [@ryan-blunden](https://community.doppler.com/u/ryan-blunden)\ **Post date:** [July 22, 2021, 1:32am UTC](https://community.doppler.com/t/anyone-having-problems-fetching-secrets-due-to-context-deadline-exceeded/98/19 "2021-07-22T01:32:22Z")
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. ---
**Author:** ![ryan-blunden](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/ryan-blunden/32/9_2.png) [@ryan-blunden](https://community.doppler.com/u/ryan-blunden)\ **Post date:** [July 22, 2021, 1:36am UTC](https://community.doppler.com/t/anyone-having-problems-fetching-secrets-due-to-context-deadline-exceeded/98/20 "2021-07-22T01:36:40Z")
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? ---
**Author:** ![iandjx](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/iandjx/32/200_2.png) [@iandjx](https://community.doppler.com/u/iandjx)\ **Post date:** [August 10, 2021, 4:12am UTC](https://community.doppler.com/t/anyone-having-problems-fetching-secrets-due-to-context-deadline-exceeded/98/21 "2021-08-10T04:12:25Z")
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, [Next page](https://community.doppler.com/t/anyone-having-problems-fetching-secrets-due-to-context-deadline-exceeded/98.md?page=2)