dispatch_protocol_error: type 100 seq 8 Error When Connecting via SSH
プラットフォームについて: Server および Data Center のみ。この記事は、Server および Data Center プラットフォームのアトラシアン製品にのみ適用されます。
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Fisheye および Crucible は除く
問題
When trying to SSH into the Stash instance, the following error is returned from the SSH client:
$ ssh -Tv user@stash.company.com
OpenSSH_4.6p1, OpenSSL 0.9.8e 23 Feb 2007
debug1: Reading configuration data /h/.ssh/config
debug1: Applying options for l1mtct00
debug1: Connecting to 10.10.10.10 [10.10.10.10] port 7999.
debug1: Connection established.
debug1: identity file /h/.ssh/id_rsa type 1
debug1: Remote protocol version 2.0, remote software version SSHD-CORE-0.7.0-ATLASSIAN-M3
debug1: no match: SSHD-CORE-0.7.0-ATLASSIAN-M3
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_4.6
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-cbc hmac-md5 none
debug1: kex: client->server aes128-cbc hmac-md5 none
debug1: sending SSH2_MSG_KEXDH_INIT
debug1: expecting SSH2_MSG_KEXDH_REPLY
debug1: Host '[10.10.10.10]:7999' is known and matches the RSA host key.
debug1: Found key in /h/.ssh/known_hosts:1
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
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 public key: /h/.ssh/id_rsa
debug1: Server accepts key: pkalg ssh-rsa blen 277
debug1: Authentication succeeded (publickey).
debug1: channel 0: new [client-session]
debug1: Entering interactive session.
dispatch_protocol_error: type 100 seq 8原因
This error is caused by trying to directly SSH into the Stash server instead of using a Git client to execute native Git operations. We've typically seen this on Windows clients using Msysgit.
ソリューション
Directly SSH'ing into Stash on port 7999 is not allowed and we only permit Git operations to occur using the SSH service provided by Stash. If you need access to the server over SSH to perform operations outside of Stash, the underlying OS will need to be configured to allow this.
Using normal Git operations such as clone are the only ones supported on the port that Stash is providing SSH access to.
There is a Suggestion raised to return a more user friendly message to administrator: STASH-3372 - Getting issue details... STATUS