Anyone having problems fetching secrets due to context deadline exceeded?

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.

Sent from Front

1 Like

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?