• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Input Plesk Obsidian, Github Cloning not working

challa

New Pleskian
I am using this method mentioned here to clone my Github repo to my httpdocs folder: Is it possible to connect to private Github repositories using Plesk Git extension?, but I am unable to connect. I always get the following error:
  • Public key for the server at 'github.com' is already known in '/var/www/vhosts/new.example.com/.ssh/git_known_hosts'.
  • Permission denied (publickey).
  • fatal: Could not read from remote repository.
  • Please make sure you have the correct access rights
  • and the repository exists.
I am not using the standard SSH port but even if I switch to the default 22, I keep getting similar errors.
My firewall is accepting connections on my SSH port and I have added the public key on the SSH section on my Github account.
HTTPS is not an option because I am cloning a shared private repo.
I am using Centos 7 with Plesk Obsidian. Everything up to date.
I tried to use the same procedure on my Plesk Onyx server and it worked fine. Same firewall settings.
Any suggestions?
Thanks.
 
I am using this method mentioned here to clone my Github repo to my httpdocs folder: Is it possible to connect to private Github repositories using Plesk Git extension?, but I am unable to connect. I always get the following error:
  • Public key for the server at 'github.com' is already known in '/var/www/vhosts/new.example.com/.ssh/git_known_hosts'.
  • Permission denied (publickey).
  • fatal: Could not read from remote repository.
  • Please make sure you have the correct access rights
  • and the repository exists https://snaptube.cam/ 9apps.
I am not using the standard SSH port but even if I switch to the default 22, I keep getting similar errors.
My firewall is accepting connections on my SSH port and I have added the public key on the SSH section on my Github account.
HTTPS is not an option because I am cloning a shared private repo.
I am using Centos 7 with Plesk Obsidian. Everything up to date.
I tried to use the same procedure on my Plesk Onyx server and it worked fine. Same firewall settings.
Any suggestions?
Thanks.
I got this solved..
 
Would you please be so kind to share the solution so that others who face the same issue can learn from it?
 
What I did is
  1. create my own id_rsa and id_rsa.pub
  2. Manually create a folder .ssh
  3. copy the two files
  4. Than add the connection to git repository
In fact, because I have many repo's linked to website on the same plesk obsidian server, my workflow is
  1. create one github user. (the machine account) assign
  2. add this user as read only in each repository on the git server (in my case github.com)
  3. copy the same id_rsa / id_rsa.pub combo to each .ssh folder in each home directory on plesk-server.
I'm almost sure we are not the only to have many domains linked with as many repositories and this pattern should be include in a user story for the backlog of the next sprint of plesk.
 
Back
Top