Locked Out of GitHub by Two-Factor Authentication

Lost the authenticator app and never saved the recovery codes. Here's GitHub's actual recovery path, why it's slower for organization-owned repositories, and why self-hosting removes the dependency on a support queue entirely.

Right now: GitHub's own recovery path

  1. Try the recovery codes generated when two-factor authentication was first set up — check a password manager or a printed copy saved at the time.
  2. If an SMS backup number was configured, GitHub can text a one-time code instead of requiring the authenticator app.
  3. If both are gone, GitHub's official account recovery form requires proving ownership (username, email history, billing details if any) and has no guaranteed turnaround — it can take days.

Why this is worse for organization repos

If the locked-out account owns an organization's repositories and no one else has admin access, there is no self-service unlock at all — recovery depends entirely on GitHub support's manual review queue, with the organization's repos inaccessible until it resolves.

Self-hosted: recovery doesn't depend on a third party's queue

On a self-hosted instance like Rithub, a site administrator can disable two-factor authentication for a locked-out account directly from the admin panel — no support ticket, no multi-day wait, because the account's "support" is whoever administers your own server, not a third party's queue.

Sign up freeImport from GitHub