Atlassian Stash v2.10.1
$ git pull
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
$ ssh -p 7999 git@<stash-server>
shell request failed on channel 0
So not an ssh/authentication issue. Was working yesterday, not working this morning, working this afternoon, not working this evening.
What could it be?
It seems that you have a SSH key uploaded but no read access to the repository in Stash as per the error below:
$ git pull fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists.
To solve that, please talk to your Stash admin so you can be assigned the right permissions.
The error below is expected because it should not be possible to get a remote shell via Stash (we use http://mina.apache.org/sshd-project/index.html for our SSH server):
$ ssh -p 7999 git@<stash-server> shell request failed on channel 0
Please refer to https://jira.atlassian.com/browse/STASH-3372
Since you say "Was working yesterday, not working this morning, working this afternoon, not working this evening", I doubt that Thiago is right about your user rights. (He might be right, but then somebody took your rights away to the repo, gave them back and took them away again.)
Confirmed, I can browse the contents of the repo on the Stash web interface. The "shell request failed on channel 0" proves there is nothing wrong with the network (server accessibility) or the ssh authentication. We are exploring a possible loading issue (tens-of-thousands of accesses, yesterday, from a CI server).
I have this same error per now. It worked earlier but not now.
I can clone using https, but not ssh. The error shown is the same as presented in this question...
In bitbucket.log there is this:
2017-10-09 18:12:52,988 INFO [ssh-scm-request-handler] jenkins @XQ6B4Fx1092x38x0 1p1nx9x 127.0.0.1 SSH - git-upload-pack '/lif/com.liferay.portal.plugins.sdk-7.0.git' c.a.b.i.ssh.server.SshCommandAdapter git was successfully authenticated via public key, but is no longer active in the underlyinguser directory. The request has been blocked
I'm pretty sure the OP would have had something similar in Stash back then...
If someone else wanders into this thread - I was accidentally sudoed into bash. Apparently that's a no go on the push - see https://confluence.atlassian.com/bitbucket/troubleshoot-ssh-issues-271943403.html
Logged off the sudo and was able to push again.
Hello! My name is Mark Askew and I am a Premier Support Engineer for products Bitbucket Server/Data Center, Fisheye & Crucible. Today, I want to bring the discussion that Jennifer, Matt, and ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs