diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2019-10-11 03:06:24 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2019-10-11 03:06:24 +0300 |
| commit | 133924c6cc443f5f69e1ab08d43b363d77677cb0 (patch) | |
| tree | e893a7d36105fc4acec7038feae5f03bd34cfc2c /doc/user/profile/account/two_factor_authentication.md | |
| parent | f607152a0802a68067343ad73f989033cb8e9a06 (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/user/profile/account/two_factor_authentication.md')
| -rw-r--r-- | doc/user/profile/account/two_factor_authentication.md | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/doc/user/profile/account/two_factor_authentication.md b/doc/user/profile/account/two_factor_authentication.md index 5721e9858f1..108d4f0b387 100644 --- a/doc/user/profile/account/two_factor_authentication.md +++ b/doc/user/profile/account/two_factor_authentication.md @@ -244,6 +244,12 @@ Sign in and re-enable two-factor authentication as soon as possible. - The user logs out and attempts to log in via `second.host.xyz` - U2F authentication fails, because the U2F key has only been registered on `first.host.xyz`. +## Troubleshooting + +If you are receiving an `invalid pin code` error, this may indicate that there is a time sync issue between the authentication application and the GitLab instance itself. + +Most authentication apps have a feature in the settings for syncing the time for the codes themselves. For Google Authenticator for example, go to `Settings > Time correction for codes`. + <!-- ## Troubleshooting Include any troubleshooting steps that you can foresee. If you know beforehand what issues |