packet_write_wait: Connection to 18.205.93.2 port 22: Broken pipe

[Green Strawberry]

alpine:~$ ssh -T git@bitbucket.org
packet_write_wait: Connection to 18.205.93.2 port 22: Broken pipe
alpine:~$
alpine:~$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 00:0c:29:0f:ad:ed brd ff:ff:ff:ff:ff:ff
inet 192.168.195.165/24 brd 192.168.195.255 scope global eth0
valid_lft forever preferred_lft forever
inet6 fe80::20c:29ff:fe0f:aded/64 scope link
valid_lft forever preferred_lft forever
alpine:~$ nmap -sT 127.0.0.1
Starting Nmap 7.70 ( https://nmap.org ) at 2019-02-26 16:36 JST
Nmap scan report for alpine.localdomain (127.0.0.1)
Host is up (0.00013s latency).
Not shown: 999 closed ports
PORT STATE SERVICE
22/tcp open ssh

Nmap done: 1 IP address (1 host up) scanned in 0.17 seconds

[Ana Retamal · Accepted solution]

Hi Green Strawberry! 

I've done some research about the error message you posted and seems like it's not an error inherently from Bitbucket, but it's caused by the session being interrupted. I found a couple of articles that might help you, you can read them here and here.

Let us know if that helps you!

Ana 

[Green Strawberry]

Dear Ana,

Thank you very much.
I tried and tried variously, but the title is still unresolved.

alpine:~$ sudo nano /etc/ssh/ssh_config
alpine:~$ cat /etc/ssh/ssh_config
# $OpenBSD: ssh_config,v 1.33 2017/05/07 23:12:57 djm Exp $

# This is the ssh client system-wide configuration file. See
# ssh_config(5) for more information. This file provides defaults for
# users, and the values can be changed in per-user configuration files
# or on the command line.

# Configuration data is parsed as follows:
# 1. command line options
# 2. user-specific file
# 3. system-wide file
# Any configuration value is only changed the first time it is set.
# Thus, host-specific definitions should be at the beginning of the
# configuration file, and defaults at the end.

# Site-wide defaults for some commonly used options. For a comprehensive
# list of available options, their meanings and defaults, please see the
# ssh_config(5) man page.

Host *
# ForwardAgent no
# ForwardX11 no
# PasswordAuthentication yes
# HostbasedAuthentication no
# GSSAPIAuthentication no
# GSSAPIDelegateCredentials no
# BatchMode no
# CheckHostIP yes
# AddressFamily any
# ConnectTimeout 0
# StrictHostKeyChecking ask
# IdentityFile ~/.ssh/id_rsa
# IdentityFile ~/.ssh/id_dsa
IdentityFile ~/.ssh/id_ecdsa
# IdentityFile ~/.ssh/id_ed25519
Port 22
# Protocol 2
# Ciphers aes128-ctr,aes192-ctr,aes256-ctr,aes128-cbc,3des-cbc
# MACs hmac-md5,hmac-sha1,umac-64@openssh.com
# EscapeChar ~
# Tunnel no
# TunnelDevice any:any
# PermitLocalCommand no
# VisualHostKey no
# ProxyCommand ssh -q -W %h:%p gateway.example.com
# RekeyLimit 1G 1h
HostName 192.168.195.165
User git
TCPKeepAlive yes
IdentitiesOnly yes

alpine:~$
alpine:~$ ssh -Tv git@bitbucket.org
OpenSSH_7.9p1, OpenSSL 1.1.1a 20 Nov 2018
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 20: Applying options for *
debug1: Connecting to 192.168.195.165 [192.168.195.165] port 22.
debug1: Connection established.
debug1: identity file /home/pure/.ssh/id_ecdsa type 2
debug1: identity file /home/pure/.ssh/id_ecdsa-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_7.9
debug1: Remote protocol version 2.0, remote software version OpenSSH_7.9
debug1: match: OpenSSH_7.9 pat OpenSSH* compat 0x04000000
debug1: Authenticating to 192.168.195.165:22 as 'git'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: curve25519-sha256
debug1: kex: host key algorithm: ecdsa-sha2-nistp256
debug1: kex: server->client cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ecdsa-sha2-nistp256 SHA256:Ex6eiJFwHaD4E6IvSiyHfDP+nLbQbAL8BHO664zW9X4
debug1: Host '192.168.195.165' is known and matches the ECDSA host key.
debug1: Found key in /home/pure/.ssh/known_hosts:1
debug1: rekey after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: rekey after 134217728 blocks
debug1: Will attempt key: /home/pure/.ssh/id_ecdsa ECDSA SHA256:riQbHKD5dMsWUwX3GzOrTF+4j+qSegwmKJylcNBdpcI
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_input_ext_info: server-sig-algs=<ssh-ed25519,ssh-rsa,rsa-sha2-256,rsa-sha2-512,ssh-dss,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521>
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,password,keyboard-interactive
debug1: Next authentication method: publickey
debug1: Offering public key: /home/pure/.ssh/id_ecdsa ECDSA SHA256:riQbHKD5dMsWUwX3GzOrTF+4j+qSegwmKJylcNBdpcI
debug1: Authentications that can continue: publickey,password,keyboard-interactive
debug1: Next authentication method: keyboard-interactive
debug1: Authentications that can continue: publickey,password,keyboard-interactive
debug1: Next authentication method: password
git@192.168.195.165's password:
Connection closed by 192.168.195.165 port 22
alpine:~$

"Connection closed by 192.168.195.165 port 22" was displayed.

Meny thanks.

[Green Strawberry]

alpine:~$ sudo nano /etc/ssh/ssh_config
[sudo] password for pure:
alpine:~$ cat /etc/ssh/ssh_config
# $OpenBSD: ssh_config,v 1.33 2017/05/07 23:12:57 djm Exp $

# This is the ssh client system-wide configuration file. See
# ssh_config(5) for more information. This file provides defaults for
# users, and the values can be changed in per-user configuration files
# or on the command line.

# Configuration data is parsed as follows:
# 1. command line options
# 2. user-specific file
# 3. system-wide file
# Any configuration value is only changed the first time it is set.
# Thus, host-specific definitions should be at the beginning of the
# configuration file, and defaults at the end.

# Site-wide defaults for some commonly used options. For a comprehensive
# list of available options, their meanings and defaults, please see the
# ssh_config(5) man page.

Host *
# ForwardAgent no
# ForwardX11 no
# PasswordAuthentication yes
# HostbasedAuthentication no
# GSSAPIAuthentication no
# GSSAPIDelegateCredentials no
# BatchMode no
# CheckHostIP yes
# AddressFamily any
# ConnectTimeout 0
# StrictHostKeyChecking ask
# IdentityFile ~/.ssh/id_rsa
# IdentityFile ~/.ssh/id_dsa
IdentityFile ~/.ssh/id_ecdsa
# IdentityFile ~/.ssh/id_ed25519
Port 22
# Protocol 2
# Ciphers aes128-ctr,aes192-ctr,aes256-ctr,aes128-cbc,3des-cbc
# MACs hmac-md5,hmac-sha1,umac-64@openssh.com
# EscapeChar ~
# Tunnel no
# TunnelDevice any:any
# PermitLocalCommand no
# VisualHostKey no
# ProxyCommand ssh -q -W %h:%p gateway.example.com
# RekeyLimit 1G 1h
HostName 192.168.195.165
User git
TCPKeepAlive yes
IdentitiesOnly yes
ClientAliveInterval 300
ClientAliveCountMax 2

alpine:~$ ssh -Tv git@bitbucket.org
OpenSSH_7.9p1, OpenSSL 1.1.1a 20 Nov 2018
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 20: Applying options for *
/etc/ssh/ssh_config: line 51: Bad configuration option: clientaliveinterval
/etc/ssh/ssh_config: line 52: Bad configuration option: clientalivecountmax
/etc/ssh/ssh_config: terminating, 2 bad configuration options
alpine:~$

Alpine Linux is a virtual machine on VMware Workstation 14 Pro.
Host OS is Windows 10 Home.
Is there anything missing in my thinking?
Thank you.

[Green Strawberry]

Dear Ana,

Thank you very much.

This thread will be closed.
Meny thanks.

[nocomer]

For those, who tried to connect to bitbucket.org through ssh from vmvare virtual machine and faced with the same issue, I found the link that can be helpful https://communities.vmware.com/thread/590825

So, setting IPQoS=throughput in ssh_config solved the issue for me.

[timvigers]

^^^

This should be a suggested answer as this solved it for me.

Just to confirm that I added IPQoS=throughput to ~/.ssh/config file.

This was on Fedora 29 running on VMWare Workstation 12.5.