Depot builder timeout + expired TLS certificate

Questions / Help Build debugging
1

My deploys have been failing for the past hour. Both Depot and BuildKit builders are unreachable.

Depot: Times out with deadline_exceeded, then fails with 401 Unauthorized
BuildKit: Loops endlessly on “Connecting to buildkit daemon… Updating
remote builder…”

The final error from Depot reveals the root cause:

failed to verify certificate: x509: certificate has expired or is not yet
valid:
current time 2026-03-17T08:32:08Z is before 2026-03-17T15:10:29Z

Looks like a TLS cert was issued with a future “not before” date (15:10:29
UTC today).

App: indiestack
Region: sjc
Builder: fly-builder-small-shadow-2162
flyctl version: latest

Tried: --buildkit, --no-cache, --depot=false, re-auth. Nothing works.

The running app is fine — just can’t push new code. Any ETA on a fix?

2

Hi, I’ve tested builders in sjc (same region you’re using) and others: I tested depot and fly native (–depot=false) and both work well.

4

I am having the same issue. An infinite loop of `Connecting to buildkit daemon at …`. Only happens with buildkit enabled

5

Hi folks!

--buildkit is decidedly experimental. It’s fine to use it but if you have issues I recommend switching to the non-experimental builders (i.e. don’t say --buildkit - this defaults to Depot builders or you can use --depot=false for Fly-native non-buildkit builders.

Cheers!