Unable to clone or pull updates from a remote Git repository to Plesk: Permission denied (publickey)

Note: The following steps illustrate an example with a remote GitHub account but there is no difference with other Git repository providers such as Bitbucket, Gitlab and others.

1. Log in to Plesk GUI

2. Go to Domains > example.com > Git > Add Repository > Select: Remote Git hosting like GitHub or BitBucket > Set the Remote Git repository. For example, GitHub: git@github.com:jdoe/myproject.git or BitBucket: git@bitbucket.org:jdoe/myproject.git

3. Copy the SSH public key of the Plesk subscription account:

   

Note: The following steps illustrate an example with a remote GitHub account but there is no difference with other Git repository providers such as Bitbucket, Gitlab and others.

1. Log in to Plesk GUI

2. Go to Domains > example.com > Git

3. Click on the Repository Settings option:

   

4. Copy the SSH public key of the Plesk subscription account:

   

Note: If the message Error: Key already in use will be displayed on GitHub, verify that the SSH public key from the Plesk subscription account is not included on other GitHub repositories or accounts. For more details, check GitHub documentation.

1. Log in to GitHub

2. In the upper-right corner of any page, click your profile photo, then click Settings:

   

3. In the user settings sidebar, click SSH and GPG keys:

   

4. Click on New SSH key:

   

5. In the Title field, add a descriptive label for the new key. For example, you might call this key: Plesk SSH key

6. Paste the Plesk subscription SSH public key into the Key field:

   

7. Click Add SSH key:

   

8. If prompted, confirm your GitHub password:

   

9. If it's a new remote Git repository, go back to Plesk and continue the cloning process by clicking on OK to apply the changes:

   

Note: If the message Someone has already registered that SSH key will be displayed on Bitbucket, verify that the SSH public key from the Plesk subscription account is not included on other Bitbucket repositories or accounts. For more details, check Bitbucket documentation.

1. Log in to Bitbucket

2. In the lower-left corner, select your avatar and click on Personal settings > Click SSH keys > Click Add key

3. Enter a Label for the new key, for example, you might call this key: Plesk SSH key

4. Paste the Plesk domain SSH public key into the Key field and click Save

5. If it's a new remote Git repository, go back to Plesk and continue the cloning process by clicking on OK to apply the changes:

   

Note: If the message Error: Key already in use will be displayed on GitLab, verify that the SSH public key from the Plesk subscription account is not included on other GitLab repositories or accounts. For more details, check GitHub documentation.

1. Log in to GitLab

2. In the top right corner, select your avatar and click on Preferences

3. From the left sidebar, click on SSH Keys

4. In the Title text box, type a descriptive name for the SSH key, for example, you might call this key: Plesk SSH key

5. In the Key text box, paste the Plesk subscription SSH public key and click on Add key

6. If it's a new remote Git repository, go back to Plesk and continue the cloning process by clicking on OK to apply the changes: