Error on remote builder: server returned a non-200 status code: 500

1

I’m reaching errors while trying to deploy a new release of my app:

$ fly deploy
==> Verifying app config
Validating /Users/username/code/my/app/fly.toml
✓ Configuration is valid
--> Verified app config
==> Building image
WARN Failed to start remote builder heartbeat: server returned a non-200 status code: 500

Error: failed to fetch an image or build from source: error connecting to docker: server returned a non-200 status code: 500

I tried to destroy the builder and recreate it, but no luck: the error persists.

After activating the logs it says this:

DEBUG --> POST https://api.fly.io/graphql

DEBUG {
  "query": "mutation($input: EnsureMachineRemoteBuilderInput!) { ensureMachineRemoteBuilder(input: $input) { machine { id state ips { nodes { family kind ip } } }, app { name organization { id slug } } } }",
  "variables": {
    "input": {
      "appName": "removed_for_privacy",
      "organizationId": null
    }
  }
}


DEBUG {}
DEBUG <-- 500 https://api.fly.io/graphql (419.3ms)

DEBUG {
  "errors": [
    {
      "message": "You hit a Fly API error with request ID: 01HT2S98TN53EPHR5PMXY06JKD-mad",
      "extensions": {
        "code": "SERVER_ERROR",
        "fly_request_id": "01HT2S98TN53EPHR5PMXY06JKD-mad"
      }
    }
  ],
  "data": {}
}

DEBUG result image:<nil> error:error connecting to docker: server returned a non-200 status code: 500

Is there anything I can do to solve this? Is it happening to anyone else?

2

Same here!

fly deploy
==> Verifying app config
Validating /Users/user/Documents/GitHub/strapi/fly.toml
✓ Configuration is valid
--> Verified app config
==> Building image
WARN Failed to start remote builder heartbeat: server returned a non-200 status code: 500

Error: failed to fetch an image or build from source: error connecting to docker: server returned a non-200 status code: 500
3

Hey folks—we’re low on capacity in the mad region right now. Unfortunately, that means that there’s frequently no room to create builders for customers who are closest to mad. Apologies for the inconvenience!

We just deployed a temporary workaround to put builders destined for mad in cdg instead. They will be a little farther away from you, but there should be capacity for them there.

If you’re still encountering trouble even with the workaround in place, please let us know!

2 Likes
4

Thanks for the update!

5

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.