When I try to use a custom git+ssh repository, the web interface reply “Repository not found or not accessible”. It seems the server fails trying to verify my ssh server ECDSA key fingerprint. Is it possible to add my fingerprint somewhere, in order to use my own git repo?
The key is d6:f0:82:75:11:1a:08:82:bf:7c:71:b4:ff:16:eb:0a for the address ridiculousglitch.com.
Thanks in advance.
If I remember right, it’s pretty important to use exactly the correct URL for the repo. Some examples are here: http://developer.playcanvas.com/en/user-manual/scripting/workflow/
It is the exact url, it’s my repo 
Heh, I mean the exact format of the URL is important…
Are you doing this: git@github.com:username/repository.git
I think you need to use the format:
ssh://git@myrepo.com:project.git
or possibly
ssh://git@myrepo.com:user/project.git
No, it’s wrong. It changes nothing. The problem, as I said in the first post, is related to the ssh fingerprint of a custom server. Also the right format for this application is ssh://user@repo.com/path/to/project. I’m not sure you know what you’re talking about.
When we clone a repository from Bitbucket or Github we do it via ssh, and you need to add your public key to your BitBucket or Github account. In your case you have a custom repository on your own server from what I understand so you need to install the public key shown in the Code tab to your server.
I think the way you install public keys on a server is by appending the public key to ~/.ssh/authorized_keys on the server (if it’s a Unix machine), but I’ve never done that so I’m not sure. That’s the basic idea anyway, does this help?
You’re right, I’ve done that already. But the web interface reply “Repository not found or not accessible”. I think it’s because playcanvas’ web server doesn’t know the fingerprint of my ssh server. The web server login process disconnect in the preauth phase of the ssh authentication. It’s the same thing it happens when you reply “no” to the ssh client, when it asks:
The authenticity of host 'yourserver.com (xxx.xxx.xxx.xxx)' can't be established.
ECDSA key fingerprint is d6:f0:82:75:11:1a:08:82:bf:7c:71:b4:ff:16:eb:0a.
Are you sure you want to continue connecting (yes/no)?I see what you mean. That may well be the case here so let me get back to you on that. It’s a holiday today in London so many of the guys are not around today - sorry for the trouble!
No problem, it’s holiday for me too
Hi,
I deployed a fix for this a few minutes ago. Can you check if you can clone your repository now? Make sure you have the public key in the Code tab in your authorized_keys file on the server.
It works, thanks a lot.