Doppler CLI Failing to Install From OS Package Registries

What to do

• Check whether your product depends on Doppler. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 42m it lasted.

  Anything that failed between 2023-03-22 22:30 UTC and 2023-03-22 23:13 UTC may need a replay.

• Subscribe to Doppler's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=doppler works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Doppler 2

1. investigatingMar 22, 2023, 10:30 PM UTC

   We're currently investigating this issue. If you need immediate availability, you can install Doppler directly from our published release artifacts instead of via your OS's package registry by running: ``` (curl -Ls --tlsv1.2 --proto "=https" --retry 3 https://cli.doppler.com/install.sh || wget -t 3 -qO- https://cli.doppler.com/install.sh) | sh ```

   provider

2. resolvedMar 22, 2023, 11:13 PM UTC

   An incident was identified at our provider for OS package registry downloads. They've fixed the issue and installs from OS package registries are available again. Impact: The incident affected all Doppler users attempting to install the Doppler CLI via their OS package registeries. This resulted in disruptions to their workflows relying on the Doppler CLI. Resolution: Cloudsmith resolved the incident after around an hour, and users were once again able to install the Doppler CLI from their OS package registries.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.