Git: connection closed by assembla.

Hi,

I had my git repository succesfuly installed since two days, and everything was working fine.
Today i wanted to do a push, and i now have this error:

Connection closed by 209.62.65.66
fatal: The remote end hung up unexpectedly

I also have the same error if i try a pull.
I tried the command ‘ssh -v git@git.assembla.com’ to see what’s happening and i’ve got this (i only paste the end of the result)

debug1: Authentications that can continue: publickey,password
debug1: Next authentication method: publickey
debug1: Trying private key: /home/steve/.ssh/identity
debug1: Offering public key: /home/steve/.ssh/id_rsa
Connection closed by 209.62.65.66

I tried to generate a new ssh key, without succes! By the way, i’m using my ssh on github, and everything is working there.
So i’m pretty sure the problem is not on my side but maybe on the assembla’s server side, who close the connection.

Any idea?

Thanks for help

It’s assembla it’s happening to me too. All my git repositories are down. Very confused at the moment

AAARGH! Me too. This is V annoying.

thank you for the report, we will fix this in 30 min.

Can someone point me to the resource for creating keys using the windows git client? I know it was somewhere here on this site, but I can’t seem to find it.

Start git-shell and try this command:

ssh-keygen -t rsa

if it does not work for you, try puttygen.exe, download it from putty project

Thank you Vitalie!
Everything is working fine again.

I’m using git version 1.5.4.4

git-shell give me the following error:

$ git shell
fatal: What do you think I am? A shell?

And I don’t want to reset my ssh keys since they are used on many other systems.

How can I access all my repos?

-Matt

Ha, I just realized that the problem wasn’t fixed. Today I get a new error message:

ERROR:gitosis.serve.main:Repository read access denied
fatal: The remote end hung up unexpectedly

:(

-Matt

This error tells you that you do not have read access to repository, try to synchronize git ssh keys.

@Vitalie thanks but I tried on 2 repos, same problem. (and I’m admin on one of the 2). I get the same I try to push:

$ git push
ERROR:gitosis.serve.main:Repository read access denied
fatal: The remote end hung up unexpectedly

I checked my profile and my ssh key is still there.

-Matt

It’s the same for me. This is not on our end. I can’t even view it from the website or the track. When I click on the track it says that the python bindings are wrong

I take that back. It’s working thank you.

Hi Vitalie, I did a key sync for Matt and he still can’t pull. He’s getting the new error now: ERROR:gitosis.serve.main:Repository read access denied fatal: The remote end hung up unexpectedly

instead of not being able to connect via SSH.

Today I had a different error:

git pull
ERROR:gitosis.serve.main:Repository read access denied
fatal: The remote end hung up unexpectedly

I’ve verified my ssh public key in my profile and preformed a “Synchronize Team SSH Keys”, but it still failed..

Fortunately clicking on the “Add more ssh keys” and adding my public key to both the read and write options worked finally..

Thanks to @felttippin trick, I was able to push my latest changes. Apparently my profile’s key isn’t used. I don’t think that the problem is properly fixed tho.

-Matt

@Vitalie: Thanks for the help. Sometimes I forget the oddest things…

Profile keys appear to still be broken (un-used). The only way to push and pull from Git is to add each team members keys to the “add more ssh keys” page in Trac. This isn’t a world-ender, but is an annoyance for those of us with multiple projects.

I’m having the same problem, being unable to push to git. I’m sure that my public key is working, because I’m using it to talk to other servers.

Where is this “add more ssh keys” page in Trac? I’ve tried adding the ssh key to the profile and also the Trac/Git tab in Assembla where there’s a link for “add more ssh keys” (for both read and write). Both methods do not seem to work, and I still get the read access denied error.

One more bump for having this problem. I seem to be able to push/pull from my development repo clone. But I cannot pull a clone onto my deployment machine. I have tried ‘ssh -v git@git.assembla.com’ and it does seem to authenticate:

debug1: Authentication succeeded (publickey).

However, it then fails on another (unrelated) issue:

ERROR:gitosis.serve.main:Need SSH_ORIGINAL_COMMAND in environment.

I saw a post by Vitalie Lazu saying that this could be because the repo is private and cannot be cloned from git://
post
But I thought that was the idea of adding more public keys to the read/write section.
Is there another way to set a repo to be “non-private”?

Just wanted to add a bump. I set up a new project tonight and getting keys from the profile is still failing. Is there somewhere else that we need to mention this issue so that it can get addressed? Is someone working on it? Thanks.

We just signed up and checked in our code. While one of our team is able to push changes I get the following error:

git push origin master
ERROR:gitosis.serve.main:Repository write access denied
fatal: The remote end hung up unexpectedly

I have generated another rsa key with no luck.

any help would be great.

David

Managed to get past the previous problem by adding my public key to my profile instead of one the git page. Now I am getting this error:

To git@git.assembla.com:droidrecord.git ba35edf..0dc19c6 master > master
/usr/lib/ruby/1.8/rubygems/custom_require.rb:27:in `gem_original_require’: no such file to load - inifile (MissingSourceFile) from /usr/lib/ruby/1.8/rubygems/custom_require.rb:27:in `require’ from /var/lib/gems/1.8/gems/activesupport-2.0.2/lib/active_support/dependencies.rb:496:in `require’ from /var/lib/gems/1.8/gems/activesupport-2.0.2/lib/active_support/dependencies.rb:342:in `new_constants_in’ from /var/lib/gems/1.8/gems/activesupport-2.0.2/lib/active_support/dependencies.rb:496:in `require’ from hooks/post-receive:23
error: hooks/post-receive exited with error code 1

Any thoughts on this problem?

Thanks,
David

I have exactly the same problem. I also added my ssh key (that does work for other purposes) to my profile and to the Git/Trac (though it only says something about read acess there). When I try to clone the repository I get:

fatal: no matching remote head

Probably because there’s not even a repository! At least that’s what I assume from the “Page not found” error I get when I click on the “Git Url” link.

And when I try to push to the repository I get the following:

ERROR:gitosis.serve.main:Repository write access denied
fatal: The remote end hung up unexpectedly

Urban

PS: I’m willing to pay for your service (it’s reasonably priced after all), but then it should work out of the box.

Urban,
you have access to your repository.

But to read it you need to push some commits first to repository, git is different from svn. subversion repository can be read if it is empty, git – no.