GitHub connections reset - sign in with GitHub again to restore GitHub deploys

Summary

GitHub connections reset - sign in with GitHub again to restore GitHub deploys

At 17:34 UTC on November 12 we reset all connections between [Fly.io](http://Fly.io) accounts and GitHub. Running apps and machines are not affected, and you have not been signed out of [Fly.io](http://Fly.io). Until you reconnect: - The dashboard may show “Your GitHub SSO token seems to have expired”. - Automatic deploys on push to a connected GitHub repository will fail. - Launching or redeploying an app from a GitHub repository in the dashboard will fail. To reconnect, sign in to [Fly.io](http://Fly.io) with GitHub again and approve the authorization screen GitHub shows. Auto-deploys for a repository resume once the person who originally connected it has done this. Deploys with flyctl, and deploys from your own GitHub Actions workflows using a [Fly.io](http://Fly.io) API token, are not affected.

• Started

  Nov 12, 2026 · 6:09 PM

• Resolved

  Nov 12, 2026 · 9:46 PM

• Duration

  3h 37m

• Severity

  None

• ◉

  Monitoring

  Nov 12 · 6:09 PM Fly.io

  At 17:34 UTC on November 12 we reset all connections between [Fly.io](http://Fly.io) accounts and GitHub. Running apps and machines are not affected, and you have not been signed out of [Fly.io](http://Fly.io). Until you reconnect: - The dashboard may show “Your GitHub SSO token seems to have expired”. - Automatic deploys on push to a connected GitHub repository will fail. - Launching or redeploying an app from a GitHub repository in the dashboard will fail. To reconnect, sign in to [Fly.io](http://Fly.io) with GitHub again and approve the authorization screen GitHub shows. Auto-deploys for a repository resume once the person who originally connected it has done this. Deploys with flyctl, and deploys from your own GitHub Actions workflows using a [Fly.io](http://Fly.io) API token, are not affected.

• ✓

  Resolved

  Nov 12 · 9:46 PM Fly.io

  At 17:34 UTC on November 12 we reset all connections between [Fly.io](http://Fly.io) accounts and GitHub. Running apps and machines are not affected, and you have not been signed out of [Fly.io](http://Fly.io). Until you reconnect: - The dashboard may show “Your GitHub SSO token seems to have expired”. - Automatic deploys on push to a connected GitHub repository will fail. - Launching or redeploying an app from a GitHub repository in the dashboard will fail. To reconnect, sign in to [Fly.io](http://Fly.io) with GitHub again and approve the authorization screen GitHub shows. Auto-deploys for a repository resume once the person who originally connected it has done this. Deploys with flyctl, and deploys from your own GitHub Actions workflows using a [Fly.io](http://Fly.io) API token, are not affected.