Git is flakey at best (on unfuddle)
|
|
I am concerned that unfuddle is committed to SVN, but has not put the effort forth to properly host git repos. BUGS: Several support tickets regarding this issue have gone with no solution. After trial and error, I found that managing my own keys is the only way I can get this working. Please make git a stable, reliable unfuddle resource. |
|
|
J, There are many reasons one might encounter the “Repository read access denied” error. In your case it is likely that Git is simply using the wrong key when attempting to authenticate. There are technical reasons why it is not possible to have the same key for two users or in two separate accounts. However, there is a simple way to make sure Git uses the correct key when authenticating. To do this you can simply add the following lines to your ~/.ssh/config file:
You will need to use the actual subdomain of your account as well as specify the correct path to your private key. You can check to see if this is working by running (minus the “\”) While this will output quite a bit of information, you should be able to see which key(s) are being sent and used for authentication.
Also, you should note that it can take up to a minute for a newly added public key to become active on the server. During this time you may not be able to connect to your repository. Finally, one other reason this error can occur is if the repository is not associated with a project or if you simply do not have permission to read the repository as defined by the project(s) with which it is associated. |
|
|
The right config (MacOS) should be: Host yoursubdomain.unfuddle.com IdentitiesOnly yes —> this would not use other keys ( id_rsa for ex.). Without this option you will have problems if you enter provide other keys (id_rsa, etc) in other unfuddle projects |
