• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.

Issue Repository BitBucket

Joouul

New Pleskian
Hello,

I've a problem with my Plesk account. I can't add a git repository on my domain. I've taked this screenshot.
I've copied the RSA key into my BitBucket repository but the problem still persists.

Someone could help me ?
 

Attachments

  • screen.png
    screen.png
    279.4 KB · Views: 13
This means that ssh-keyscan -H bitbucket.org has failed to retrieve any keys. This may happen due to a number of reasons, including networking issues between your box and BitBucket.

As a workaround you may try either of the following:
  1. Use SSH on port 443 as suggested at the bottom of https://confluence.atlassian.com/bitbucket/use-the-ssh-protocol-with-bitbucket-cloud-221449711.html (basically you would only need to adjust repository URL that you pass to Plesk)
  2. Manually add public SSH host key for bitbucket.org into .ssh/git_known_hosts file (e.g. try to clone repo via shell under the respective user, then copy .ssh/known_hosts file)
 
The SSH key, must be copied into my BitBucket project "My project > Settings > Deployement Keys" or into my own BitBucket account "Account > Integration > SSH Keys ???

And I tried toadd manually this key into .ssh/git_known_hosts file (see screenshot) but don't work :(screenshot02.png
 
SSH public keys (deployment keys) are used for client identification. Host public keys (which are stored in .ssh/git_known_keys file in this case) are used for server identification. These are two different entities.

I suggest trying option (1) that was outlined in the previous post -- just adapt repository URL you specify in Plesk.
 
Back
Top