Hello. I'm getting this error when trying to connect to Stash via SSH. From the logs, it looks like it is authenticating and then exiting out.
On MacOS 10.10/Yosemite.
XXXXXXX:.SSH XXXXXXX$ ssh -p 7999 -i /Users/XXXXXXX/.SSH/key -vT XXXXXXX@XXXXXXX
OpenSSH_6.2p2, OSSLShim 0.9.8r 8 Dec 2011
debug1: Reading configuration data /etc/ssh_config
debug1: /etc/ssh_config line 20: Applying options for *
debug1: Connecting to XXXXXXX [XXXXXXX] port 7999.
debug1: Connection established.
debug1: identity file /Users/XXXXXXX/.SSH/XXXXXXX type 1
debug1: identity file /Users/XXXXXXX/.SSH/XXXXXXX type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.2
debug1: Remote protocol version 2.0, remote software version SSHD-CORE-0.9.0-ATLASSIAN-5
debug1: no match: SSHD-CORE-0.9.0-ATLASSIAN-5
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr hmac-md5 none
debug1: kex: client->server aes128-ctr hmac-md5 none
debug1: sending SSH2_MSG_KEXDH_INIT
debug1: expecting SSH2_MSG_KEXDH_REPLY
debug1: Server host key: RSA XXXXXXX
debug1: Host '[XXXXXXX]:7999' is known and matches the RSA host key.
debug1: Found key in /Users/XXXXXXX/.ssh/known_hosts:3
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: Roaming not allowed by server
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Offering RSA public key: /Users/XXXXXXX/.SSH/XXXXXXX
debug1: Server accepts key: pkalg ssh-rsa blen 279
debug1: Authentication succeeded (publickey).
Authenticated to XXXXXXX ([XXXXXXX]:7999).
debug1: channel 0: new [client-session]
debug1: Entering interactive session.
shell request failed on channel 0
Stash doesn't support a login shell over SSH. You can clone or push repositories over SSH using git (it runs the
git-receive-pack commands on the server) or you can run the
whoami command (which prints your username) using:
$ ssh -p 7999 -i /Users/XXXXXXX/.SSH/key XXXXXXX@XXXXXXX whomami
The output you copied above looks fine to me.
Hi Tim, Thanks for the info.
What I'm trying to accomplish is for a web server to reference the project location (i.e., files), so that once the changes are pushed to Stash, the web server is immediately showing the updated files I'm trying to do this by either:
a: the web server references the files directly from Stash's home directory (for example)
b: to have a post-receive action that pushes the files to another location on the server like this:
git --work-tree=/www/projectname/branch checkout -f $branch
Do you have any suggestions on how I can accomplish this?
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot