Open halostatue opened 5 years ago
Similar to #251, I’m getting Connection to UNKNOWN port 65535: Broken pipe on some, but not all, git operations.
Connection to UNKNOWN port 65535: Broken pipe
Krypton ▶ Requesting SSH authentication from phone Krypton ▶ Success. Request Allowed ✔ Enumerating objects: 33, done. Counting objects: 100% (33/33), done. Delta compression using up to 4 threads Compressing objects: 100% (21/21), done. Writing objects: 100% (21/21), 22.64 KiB | 2.26 MiB/s, done. Total 21 (delta 11), reused 0 (delta 0) packet_write_wait: Connection to UNKNOWN port 65535: Broken pipe fatal: the remote end hung up unexpectedly fatal: the remote end hung up unexpectedly
These events correspond to our IDS system (Meraki) detecting an SSH_EVENT_RESPOVERFLOW event.
SSH_EVENT_RESPOVERFLOW
I am not getting any errors on ssh -vv git@bitbucket.org or ssh -vv me.krypt.co, only on (mostly) code pushes to bitbucket.
ssh -vv git@bitbucket.org
ssh -vv me.krypt.co
Using Krypton 2.4.2.
Try the auto keep alive: https://askubuntu.com/questions/127369/how-to-prevent-write-failed-broken-pipe-on-ssh-connection
Similar to #251, I’m getting
Connection to UNKNOWN port 65535: Broken pipe
on some, but not all, git operations.These events correspond to our IDS system (Meraki) detecting an
SSH_EVENT_RESPOVERFLOW
event.I am not getting any errors on
ssh -vv git@bitbucket.org
orssh -vv me.krypt.co
, only on (mostly) code pushes to bitbucket.