Ok, so: problem solved by stepping away from the machine and coming back a 
bit later.

What was the issue?
I had multiple VM's running (test kitchen) and had them on the same IP - so 
I was basically SSH'ing into another machine than the one that was serving 
the UI...

Well, that was easy then! ;-)

Have a great weekend,
David

On Friday, 5 August 2016 16:13:46 UTC+1, David Joos wrote:
>
> Hi there,
>
> I've set up a GoCD server (16.7.0 
> (3819-b0b9921bdea58101121cc181d697355177d2f197) where /var/go/.ssh has an 
> id_rsa, with the go user's key (ie. machine user - 
> https://developer.github.com/guides/managing-deploy-keys/#machine-users).
>
> From the command line I'm able to "check the connection" via `sudo -u go 
> git ls-remote [email protected]:someowner/somerepo.git refs/heads/master` 
> without any issue, however when making use of the UI 
> (/go/admin/pipeline/new) [email protected]:someowner/somerepo.git I get...
> Error performing command: --- Command --- git ls-remote 
> [email protected]:someowner/somerepo.git refs/heads/master --- Environment --- 
> {GIT_ALLOW_PROTOCOL=http:https:ssh:git:file:rsync} --- INPUT ---- --OUTPUT 
> --- --- ERROR --- STDERR: Host key verification failed. STDERR: fatal: 
> Could not read from remote repository. STDERR: STDERR: Please make sure you 
> have the correct access rights STDERR: and the repository exists. ---
>
> I'm probably overlooking something here - anyone got an idea why would 
> there be a discrepancy between the feedback I get from the command line and 
> the UI for the go user's checking of the connection?
>
> Thanks in advance for your help!
>
> Kind regards,
> David
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to