GitHub errors and common problems

Locked out by 2FA: Lost phone, app or recovery codes

Means

You can no longer give the two-factor code, for example after losing or resetting your phone. GitHub Support cannot turn off 2FA for you, so you need one of your own recovery options.

First step

Sign in at github.com/login and choose 2FA recovery code under More options, then enter one of your saved codes. All steps

Git password rejected: Git over HTTPS needs a token now

Means

Git asks for a password and then fails with an authentication error. GitHub removed password sign-in for Git, so HTTPS pushes and pulls need a personal access token or a credential helper.

First step

Create a personal access token in your GitHub settings. All steps

Push rejected for large file: Files over 100 MiB are blocked

Means

The push fails because a commit holds a file that is too big. GitHub blocks files larger than 100 MiB and warns about files over 50 MiB.

First step

Remove the big file from the commit with git rm --cached and amend the commit. All steps

Permission denied (publickey).: GitHub did not accept your SSH key

Means

GitHub refused the SSH connection. GitHub says the usual causes are no key loaded in your SSH agent, a key that is not added to your account, the wrong user in the remote URL, or running Git with sudo.

First step

Run ssh -vT [email protected] to check that you reach GitHub on port 22. All steps

Repository not found: Wrong URL or no access to the repo

Means

Git could not find the repository. GitHub says it either does not exist under that name or your account has no permission to see it.

First step

Copy the clone URL from the repository page instead of typing it. All steps