Resolved GIT - Issue with known_hosts File / Ports?

[Powie]

We have our own Gitlab, offering SSH at port 2224. We have absolutely no problem in using Gitlab with ceratin tools.
The Plesk Extension isn't possible to connect to gitlab. I think it's a problem by the extension and how known_host are stored.
As the SSH user of the domain I can pull and push to my gitlab repo without problems. If I try to add the repo in Plesk it ends with:

• Cloning into bare repository '/var/www/vhosts/xyz123.de/git/tourtracker-web.git'...
• Server at 'gitlab.xxxxxxxxxx.net:2224' is seen for the first time.
• Adding its public key to the list of known hosts in '/var/www/vhosts/xyz123.de/.ssh/git_known_hosts_with_port_2224'.
• Failed to gather public SSH host key for the 'gitlab.be-webspace.net:2224'.
• Known hosts file '/var/www/vhosts/xyz123.de/.ssh/git_known_hosts_with_port_2224' doesn't exist
• fatal: Could not read from remote repository.
• Please make sure you have the correct access rights
• and the repository exists.

Keys are checked and works on SSH directly......

 

[IgorG]

Try to use solution from this KB article Unable to add remote git repository with ssh key using Git extension: Could not read from remote repository

 

[Powie]

Wow... Thx @IgorG .. The fix works!

 

[Powie]

And just as an addon. Via https it's possible to add a repo by:

https://gitlab-ci-token:<TOKEN>@gitlab.......

If I try this, Plesk responds with" this an unsecure password". .......

 

[mudassar]

Try to use solution from this KB article Unable to add remote git repository with ssh key using Git extension: Could not read from remote repository

this article is down?