Cannot deploy from GitHub Actions: Failed to start remote builder heartbeat: Not authorized to deploy this app

Questions / Help
1

I currently cannot deploy from GitHub Actions. It is an Elixir app, hosted in AMS. I can deploy via the cli with “fly deploy”. The error I’m getting on GitHub is:

==> Building image
WARN Failed to start remote builder heartbeat: Not authorized to deploy this app.
WARN Failed to start remote builder heartbeat: Not authorized to deploy this app.
Error: failed to fetch an image or build from source: Not authorized to deploy this app.
Error: Process completed with exit code 1.
##[debug]Finishing: Run flyctl deploy --remote-only

This happened before. What is interesting: I wanted to kill the builder to restart it. When I checked with fly apps list, there was no builder running. After I deployed manually via fly cli it is back.

Could it be that the builder gets killed after some time and is not restarted from GitHub Actions?

Thanks for your help.

Full Github debug log:

##[debug]Evaluating condition for step: 'Run superfly/flyctl-actions/setup-flyctl@master'
##[debug]Evaluating: success()
##[debug]Evaluating success:
##[debug]=> true
##[debug]Result: true
##[debug]Starting: Run superfly/flyctl-actions/setup-flyctl@master
##[debug]Loading inputs
##[debug]Loading env
Run superfly/flyctl-actions/setup-flyctl@master
##[debug]isExplicit: 0.2.68
##[debug]explicit? true
##[debug]checking cache: /opt/hostedtoolcache/flyctl/0.2.68/x64
##[debug]not found
Downloading flyctl 0.2.68 from https://github.com/superfly/flyctl/releases/download/v0.2.68/flyctl_0.2.68_Linux_x86_64.tar.gz...
##[debug]Downloading https://github.com/superfly/flyctl/releases/download/v0.2.68/flyctl_0.2.68_Linux_x86_64.tar.gz
##[debug]Destination /home/runner/work/_temp/fbb26712-b390-42db-a183-6fe72e91d50b
##[debug]download complete
##[debug]Checking tar --version
##[debug]tar (GNU tar) 1.34
##[debug]Copyright (C) 2021 Free Software Foundation, Inc.
##[debug]License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>.
##[debug]This is free software: you are free to change and redistribute it.
##[debug]There is NO WARRANTY, to the extent permitted by law.
##[debug]
##[debug]Written by John Gilmore and Jay Fenlason.
/usr/bin/tar xz -v --warning=no-unknown-keyword --overwrite -C /home/runner/work/_temp/555c16d5-c878-4699-bf09-a888c98f5a72 -f /home/runner/work/_temp/fbb26712-b390-42db-a183-6fe72e91d50b
flyctl
##[debug]Caching tool flyctl 0.2.68 x64
##[debug]source dir: /home/runner/work/_temp/555c16d5-c878-4699-bf09-a888c98f5a72
##[debug]destination /opt/hostedtoolcache/flyctl/0.2.68/x64
##[debug]finished caching tool
flyctl 0.2.68 is installed
##[debug]Node Action run completed with exit code 0
##[debug]Finishing: Run superfly/flyctl-actions/setup-flyctl@master
1s
##[debug]Evaluating: secrets.FLY_API_TOKEN
##[debug]Evaluating Index:
##[debug]..Evaluating secrets:
##[debug]..=> Object
##[debug]..Evaluating String:
##[debug]..=> 'FLY_API_TOKEN'
##[debug]=> '***'
##[debug]Result: '***'
##[debug]Evaluating condition for step: 'Run flyctl deploy --remote-only'
##[debug]Evaluating: success()
##[debug]Evaluating success:
##[debug]=> true
##[debug]Result: true
##[debug]Starting: Run flyctl deploy --remote-only
##[debug]Loading inputs
##[debug]Loading env
Run flyctl deploy --remote-only
##[debug]/usr/bin/bash -e /home/runner/work/_temp/6350fb3b-9e9c-4d65-b814-324061cebd10.sh
==> Verifying app config
Validating /home/runner/work/my_app/my_app/fly.toml
--> Verified app config
✓ Configuration is valid
==> Building image
==> Building image
WARN Failed to start remote builder heartbeat: Not authorized to deploy this app.
WARN Failed to start remote builder heartbeat: Not authorized to deploy this app.
Error: failed to fetch an image or build from source: Not authorized to deploy this app.
Error: Process completed with exit code 1.
##[debug]Finishing: Run flyctl deploy --remote-only
2

Same here - our last deployment from ~ 2 hours ago succeeded, all deployments afterwards fail. Is fly down?

Run flyctl deploy --remote-only
Validating /home/runner/work/my-project/fly.toml
✓ Configuration is valid
WARN Failed to start remote builder heartbeat: Not authorized to deploy this app.
==> Verifying app config

--> Verified app config
WARN Failed to start remote builder heartbeat: Not authorized to deploy this app.
==> Building image
==> Building image

Error: failed to fetch an image or build from source: Not authorized to deploy this app.
Error: Process completed with exit code 1.
3

I’m seeing the same thing. Also seems related to Error: failed to fetch an image or build from source: Not authorized to deploy this app.

If it helps anyone figure this out, these are the logs I’m seeing in Github Actions: use LOG_LEVEL=debug in fly deploy · alostsock/craftingway@fb512b3 · GitHub, which were generated from

flyctl doctor
LOG_LEVEL=debug flyctl deploy --verbose --remote-only

Here’s the relevant (as far as I can tell) bits of debug output:

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

DEBUG trying remote docker daemon
DEBUG {
  "query": "query ($appName: String!) { app(name: $appName) { id name organization { id slug paidPlan remoteBuilderApp { id name hostname deployed status version appUrl platformVersion currentRelease { evaluationId status inProgress version } ipAddresses { nodes { id address type createdAt } } organization { id slug paidPlan } imageDetails { registry repository tag digest version } machines{ nodes { id name config state region createdAt app { name } ips { nodes { family kind ip maskSize } } host { id } } } postgresAppRole: role { name } limitedAccessTokens { nodes { id name expiresAt } } } } } }",
  "variables": {
    "appName": "servingway-preview"
  }
}


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

DEBUG {
  "data": {
    "app": {
      "id": "servingway-preview",
      "name": "servingway-preview",
      "organization": {
        "id": "yw2NK09lG62eytyo75jV2OwzbVTey2Vjy",
        "slug": "personal",
        "paidPlan": false,
        "remoteBuilderApp": null
      }
    }
  }
}

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

DEBUG {
  "query": "mutation($input: CreateAppInput!) { createApp(input: $input) { app { id name organization { slug } config { definition } regions { name code } } } }",
  "variables": {
    "input": {
      "organizationId": "yw2NK09lG62eytyo75jV2OwzbVTey2Vjy",
      "name": "fly-builder-long-sun-6794",
      "preferredRegion": "",
      "appRoleId": "remote-docker-builder",
      "machines": true
    }
  }
}


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

DEBUG {
  "data": {
    "createApp": null
  },
  "errors": [
    {
      "message": "Not authorized to deploy this app.",
      "locations": [
        {
          "line": 1,
          "column": 37
        }
      ],
      "path": [
        "createApp"
      ],
      "extensions": {
        "code": "UNAUTHORIZED"
      }
    }
  ]
}
4

Hi folks,

tl;dr to fix this, run fly deploy from your laptop or other machine where you’ve done a full fly auth login authentication.

Explanation:

We’ve tracked this down to the following: Inactive builders are deleted after several days. When you run a deploy a new builder is created, so typically this behavior is transparent.

However, we’ve noticed that when there are no active builders and a deploy is started with a deploy-only token (typically seen in CI like Github, CircleCI and others), that token doesn’t have authorization to create a new builder. The error you see actually refers to being unable to deploy the builder app, not your own app.

The workaround we’ve identified is for you to run fly deploy --build-only from e.g. your laptop using a fully-authenticated fly session; i.e. one where you log in using fly auth login . That will create a new builder, and CI-driven deploys should then work.

We’re looking at fixing this so a deploy is always able to create a new builder so this doesn’t impact you or other users again.

  • Daniel
3 Likes
5

Thanks @roadmr, that makes sense. I had a feeling that the reason was the missing (or not running) builder and in the past doing a manual deploy fixed the issue for some time. I can also confirm that the issue appeared after I did not deploy for several days.

6

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