GitHub: Cloning or pushing results in "Broken pipe" error

Saturday, June 1 2019 · Lesezeit: 2 Minuten · 243 Wörter Achtung! Dieser Artikel ist älter als ein Jahr. Der Inhalt ist möglicherweise nicht mehr aktuell!

Something strange happens at the moment with my GitHub interaction over ssh. I get the following error when trying to interact (push, pull, clone) with any repo. That has something to do with ssh.
The GitHub help page suggest issuing the following command:

ssh -T git@github.com

It should print out your username. If that happens your ssh works and GitHub can authenticate you. However my result differs a bit:

git clone git@github.com:vlcty/ansible-endlessh.git
Cloning into 'ansible-endlessh'...
packet_write_wait: Connection to 140.82.118.4 port 22: Broken pipe
fatal: Could not read from remote repository.

Please make sure you have the correct access rights

For some reasons something is not right. I should note that this happens currently on MacOS. First I thought my firewall is blocking traffic.
I’ve copied my identity into an Archlinux docker container (running on the same MacBook) and everything works. So it has definately something to do with MacOS ssh client.

I searched the web but was not able to find someone else with that problem. So it must be something wron with my Macbook.

A solution for now is adding the following snippet into my local ssh config (~/.ssh/config):

Host github.com
	ServerAliveInterval 600
	TCPKeepAlive yes
	IPQoS=throughput

Now everything works again but interactions are very slow.

:-$ ssh -T git@github.com
Hi vlcty! You've successfully authenticated, but GitHub does not provide shell access.

My problem only occures when interacting with GitHub. My GitLab installation or communicating with a normal ssh daemon works fine. Strange.

Du hast einen Kommentar, einen Wunsch oder eine Verbesserung? Schreib mir doch eine E-Mail! Die Infos dazu stehen hier.

🖇️ = Link zu anderer Webseite
🔐 = Webseite nutzt HTTPS (verschlüsselter Transportweg) Zurück