http://unfuddle.com/community Unfuddle Community Forums www.unfuddle.com/community:3:730:1990 http://www.unfuddle.com/community/forums/3/topics/730 I am concerned that unfuddle is committed to SVN, but has not put the effort forth to properly host git repos. BUGS: - Cannot have the same rsa-key assigned to more than one user account, although I may have more than one account on my machine. - As a 'work-around', unfuddle offers to store more than one key. Unfortunately, it only seems to pass Git the first rsa-key. As a result, I have to delete my 'home' key every morning when I get to work and re-enter my 'work' key. Reverse process at home. IF I do not 'manage' my own keys, I get ERROR:gitosis.serve.main:Repository read access denied fatal: The remote end hung up unexpectedly which is undoubtedly a server-side issue. 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. Tue, 25 Aug 2009 16:58:05 UTC JDStraughan www.unfuddle.com/community:3:730:2303 http://www.unfuddle.com/community/forums/3/topics/730 The right config (MacOS) should be: Host yoursubdomain.unfuddle.com User git IdentityFile /path/to/correct/private/key_rsa IdentitiesOnly yes 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 Wed, 06 Jan 2010 23:20:39 UTC Dmitry Naumov www.unfuddle.com/community:3:730:2002 http://www.unfuddle.com/community/forums/3/topics/730 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: <pre><code>Host yoursubdomain.unfuddle.com User git IdentityFile /path/to/correct/private/key_rsa </code></pre> 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 "\") <pre><code>ssh -vv git\@yoursubdomain.unfuddle.com</code></pre> 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. Thu, 27 Aug 2009 01:31:46 UTC David C.