• Error: HTTP Basic: Access denied. The provided password or token ...
• Error: “invalid pin code”
• Error: “Permission denied (publickey)” when regenerating recovery codes
• Recovery options and 2FA reset
  • Use a saved recovery code
  • Generate new recovery codes using SSH
  • Disable and reset 2FA on your account

Troubleshooting two-factor authentication

Error: HTTP Basic: Access denied. The provided password or token ...

When making a request, you can receive the following error:

HTTP Basic: Access denied. The provided password or token is incorrect or your account has 2FA enabled and you must use a personal
access token instead of a password.

This error occurs in the following scenarios:

• You have 2FA enabled and have attempted to authenticate with a username and password.
• You do not have 2FA enabled and have sent an incorrect username or password with your request.
• You do not have 2FA enabled but an administrator has enabled the enforce 2FA for all users setting.
• You do not have 2FA enabled, but an administrator has disabled the password authentication enabled for Git over HTTP(S) setting.

Instead you can authenticate:

• Using a personal access token (PAT):
  • For Git requests over HTTP(S), a PAT with read_repository or write_repository scope is required.
  • For GitLab container registry requests, a PAT with read_registry or write_registry scope is required.
  • For Dependency Proxy requests, a PAT with read_registry and write_registry scopes is required.
• If you have configured LDAP, using an LDAP password
• Using an OAuth credential helper.

Error: “invalid pin code”

If you receive an invalid pin code error, this can indicate that there is a time sync issue between the authentication application and the GitLab instance itself. To avoid the time sync issue, enable time synchronization in the device that generates the codes. For example:

• For Android (Google Authenticator):
  1. Go to the Main Menu in Google Authenticator.
  2. Select Settings.
  3. Select the Time correction for the codes.
  4. Select Sync now.
• For iOS:
  1. Go to Settings.
  2. Select General.
  3. Select Date & Time.
  4. Enable Set Automatically. If it’s already enabled, disable it, wait a few seconds, and re-enable.

Error: “Permission denied (publickey)” when regenerating recovery codes

If you receive a Permission denied (publickey) error when attempting to generate new recovery codes using an SSH key and you are using a non-default SSH key pair file path, you might need to manually register your private SSH key using ssh-agent.

Recovery options and 2FA reset

If you don’t have access to your code generation device and are unable to sign into your account, the following recovery options are available:

• If you saved your recovery codes when you enabled 2FA, use a saved recovery code.
• If you don’t have your recovery codes but have an SSH key, generate new recovery codes using SSH.
• If you don’t have your recovery codes or an SSH key, disable and reset 2FA on your account

Use a saved recovery code

To use a recovery code:

1. Enter your username or email, and password, on the GitLab sign-in page.
2. When prompted for a two-factor code, enter the recovery code.

After you use a recovery code, you cannot re-use it. You can still use the other recovery codes you saved.

Generate new recovery codes using SSH

If you forget to save your recovery codes when enabling 2FA, and you added an SSH key to your GitLab account, you can generate a new set of recovery codes with SSH:

1. In a terminal, run:

   ssh git@gitlab.com 2fa_recovery_codes
   

   On self-managed instances, replace gitlab.com in the command above with the GitLab server hostname (gitlab.example.com).

2. You are prompted to confirm that you want to generate new codes. This process invalidates previously-saved codes. For example:

   Are you sure you want to generate new two-factor recovery codes?
   Any existing recovery codes you saved will be invalidated. (yes/no)
   
   yes
   
   Your two-factor authentication recovery codes are:
   
   119135e5a3ebce8e
   11f6v2a498810dcd
   3924c7ab2089c902
   e79a3398bfe4f224
   34bd7b74adbc8861
   f061691d5107df1a
   169bf32a18e63e7f
   b510e7422e81c947
   20dbed24c5e74663
   df9d3b9403b9c9f0
   
   During sign in, use one of the codes above when prompted for your
   two-factor code. Then, visit your Profile Settings and add a new device
   so you do not lose access to your account again.
   

3. Go to the GitLab sign-in page and enter your username or email, and password. When prompted for a two-factor code, enter one of the recovery codes obtained from the command-line output.

After signing in, immediately set up 2FA with a new device.

Disable and reset 2FA on your account

If other methods are unavailable, create a support ticket to request a GitLab global administrator to disable 2FA for your account.

This service is only available for accounts that have a GitLab.com subscription. For more information, see our blog post.

1. Go to GitLab Support.
2. Select Submit a Ticket.
3. If possible, sign into your account.
4. In the issue dropdown list, select GitLab.com user accounts and login issues.
5. Complete the fields in the support form.
6. Select Submit.

Disabling this setting temporarily leaves your account in a less secure state. You should sign in and re-enable 2FA as soon as possible.

If you are a top-level Owner of a namespace on a paid plan, you can disable 2FA for enterprise users. For more information, see Disable two-factor-authentication.