Error: No access token available. Please login with 'flyctl auth login'

Error: No access token available. Please login with 'flyctl auth login'

TL;DR: in GitHub Actions this almost always means the FLYAPITOKEN secret is in the wrong place. Move it from Environment secrets to Repository secrets (or scope the job to that environment), and make sure the deploy step actually receives it. Locally, the fix is just flyctl auth login.

Error: No access token available. Please login with 'flyctl auth login'

Steps

1. Check where the secret lives: repo Settings → Secrets and variables → Actions. If FLYAPITOKEN sits under Environment secrets but the job has no environment: key, the step cant see it — GitHub only injects environment secrets into jobs that declare that environment.
2. Move it: delete the secret from Environment secrets and re-add it under Repository secrets. Alternative: add the matching environment: [name] to the job.
3. Make sure the deploy step exports the secret so flyctl can read it.
4. Re-run the workflow. Expected: flyctl deploy proceeds past auth instead of erroring.
5. Local variant:

flyctl auth login
flyctl auth whoami

Expected: whoami prints your email.

When this applies

• the exact error in GitHub Actions or any CI, with exit code 1
• the secret exists but the step still cant see it (wrong secret scope, or env not wired into the step)

When it doesnt

• flyctl auth login failing on your laptop — that is a browser or terminal problem, not secret placement
• token was revoked in the fly.io dashboard — mint a fresh one and update the secret

Compatibility

flyctl 0.x, flyctl-actions/setup-flyctl.

Why it happens

GitHub scopes secret injection by environment. A job without an environment: key never receives environment secrets, so FLYAPITOKEN arrives empty, and flyctl treats empty as absent — hence the misleading "please login" message even though you configured everything.

Edge cases

• validate the secret is non-empty early in the workflow so the failure message is obvious instead of cryptic
• prefer short-lived deploy tokens over long-lived personal tokens in CI
• never echo the token into logs; GitHub masks secrets but scripts can leak prefixes

Find this skill again

curl -s 'https://vectle.com/api/v1/search?q=flyctl+no+access+token+flyctl+auth+login'

A flyctl user deploying from GitHub Actions had FLYAPITOKEN configured yet every run failed with Error: No access token available. Please login with 'flyctl auth login'. The verified fix: the token had been saved as an Environment secret while the job declared no environment, so the step never received it — moving it to Repository secrets (or scoping the job to the environment) fixed the deploy. Source: https://github.com/superfly/flyctl/issues/1787