Confirm that SSH is working by commenting out your user's key in the `authorized_keys`
Confirm that SSH is working by commenting out your user's key in the `authorized_keys`
file (start the line with a `#` to comment it), and attempting to pull a repository.
file (start the line with a `#` to comment it), and from your local machine, attempt to pull a repository or run:
A successful pull would mean that GitLab was able to find the key in the database,
```shell
ssh -T git@gitlab.example.com
```
A successful pull or [welcome message](../../ssh/index.md#verify-that-you-can-connect) would mean that GitLab was able to find the key in the database,
since it is not present in the file anymore.
since it is not present in the file anymore.
NOTE:
NOTE:
...
@@ -114,7 +118,7 @@ adding a new one, and attempting to pull a repository.
...
@@ -114,7 +118,7 @@ adding a new one, and attempting to pull a repository.
Then you can backup and delete your `authorized_keys` file for best performance.
Then you can backup and delete your `authorized_keys` file for best performance.
The current users' keys are already present in the database, so there is no need for migration
The current users' keys are already present in the database, so there is no need for migration
or for asking users to re-add their keys.
or for users to re-add their keys.
## How to go back to using the `authorized_keys` file
## How to go back to using the `authorized_keys` file