Terraform runs failing due to expired HashiCorp signing key

What to do

• Check whether your product depends on Spacelift. 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 21h 36m it lasted.

  Anything that failed between 2026-04-20 11:43 UTC and 2026-04-21 09:20 UTC may need a replay.

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

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

Updates from Spacelift 3

1. monitoringApr 20, 2026, 11:43 AM UTC

   We identified that Terraform runs were failing when downloading the Terraform binary. The public GPG key we use to verify HashiCorp's checksum signatures had expired, causing every binary download to fail signature verification. Runs using OpenTofu or a Custom workflow were not affected. A fix updating the embedded HashiCorp public key has been rolled out during the week-end across our managed infrastructure. If you are using private worker pools, you will need to cycle your worker pool so the workers pick up the latest launcher version that includes the fix. Until workers are cycled, new Terraform runs on those pools will continue to fail. Cycling worker pool is not required if using kubernetes native workers. This is only to make sure EC2 docker based workers are refreshed. Action required for Self-Hosted: Hotfix v5.1.1 has been published and can be used to resolve the issue on Self-Hosted installations on v5.1.0. If you are on an older Self-Hosted version, please contact your Spacelift account team — we are publishing targeted hotfixes on request. If you cannot upgrade right now, you can unblock Terraform runs by: - Switch from Terraform to OpenTofu if you can. - Switch to a custom workflow for your stack and provide Terraform binary yourself - Setting "skipVendorBinaryDownload: true" on the affected stacks, and running those stacks in a runner image that already has the terraform binary installed at the expected path.

   provider

2. monitoringApr 21, 2026, 8:32 AM UTC

   We are continuing to monitor for any further issues.

   provider

3. resolvedApr 21, 2026, 9:20 AM UTC

   If self hosted customer are still affected, please reach out to our support team.

   provider

Corrections

None so far.

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