• 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!
  • 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.

Issue Github integration errors. Unable to pull updates from the remote repository.

I am using this method mentioned here: 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.domain.com/.ssh/git_known_hosts'.
ssh: connect to host github.com port 49153: Connection timed out
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.


Even if I try changing the SSH port to the default 22, I keep getting similar errors.

Any suggestions what the issue could be?

Using Centos 7 with Plesk Obsidian.

Thanks.
 
So, with SSH port 22 and the same settings on a Plesk Onyx server this is working no problem. It might be an issue with Plesk Obsidian and the Git extension.
 
Anyway, issue is solved by deleting id_rsa, id_rsa.pub and known_hosts file from the .ssh folder. You will have to re-copy the ssh key and clone the repo again.
 
Back
Top