← Back to Fly.io History
none✓ Resolved

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

Fly.io•
Status
resolved
Duration
3h 37m
Updates
2
Coverage
0 articles

INCIDENT TIMELINE

✓ Resolved
This incident has been resolved.
resolved
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.
monitoring
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.

📊 TECHNICAL DETAILS

Internal ID
8cf0bbe0-99e0-46aa-83d5-d74c9bd16602
External ID
01M78F5YHXG03WMZ4E3MMDTZ4B
🕐 First reported
🔄 Last Updated
✓ Resolved
NONE
Impact Level
3h 37m
Total Duration
2
Status Updates
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we request generation of one.
0 / 100 requests100 more needed