Then I tried pushing the changes that were waiting politely to be transported safely over to the repository, and what I was greeted with was a truly incredibly sight to behold. To test the routing was complete I ran the same command I had run before, $ ssh -T and saw the same friendly greeting I had before.
#Gitkraken fetch failed for origin update#
I went ahead and followed the second step listed on the article, which was to update my ssh config to route github connections through the HTTPS port. It was like finding a radio linked directly to the forrest rangers after being lost in the forrest for 2 weeks, it was absolutely beautiful. Hi aesinv! You 've successfully authenticated, but GitHub does not provide shell access.
I was supposed to receive a friendly success message back, so I went ahead and gave it a go: $ ssh -T - p 443. The first was an altered version of the first command that essentially ran the same check but through a different port. After restarting 4 times with no luck I did more searching and found myself on the following page on Github Help: Using SSH over the HTTPS port. However with my repo already on https and it still not working, I had to explore other avenues to fix it. That was a no-go, but the first command to double check came in handy: $ ssh -T git post mentioned that should timeout, and it did. After some Googlin' I was able to find a Stack overflow post mentioning the same issue, with the accepted answer saying to change the repo URL from SSH to https. Please make sure you have the correct access rightsĪlright. Ssh: connect to host port 22: Operation timed outįatal: Could not read from remote repository. After remaining idle for quite a while, the command would fail with the following: $ git push
Since I use SSH with Github, I was able to circumvent the issue briefly by changing the origin to https then providing my user/pass when pushing and pulling but all of a sudden that stopped working completely as well. Out of the blue I was unable to pull or push to any repos. It's amazing how difficult it was to find an actual fix for this, although due to the network-related nature of the issue I can imagine there are at least 400 million different fixes and causes. There's nothing worse than losing precious development time thanks to some random sporadic tooling error.
#Gitkraken fetch failed for origin code#
Fixing git push/pull timing out Here's what I did to fix a random git timeout that prevented me from pushing or pulling code for hours.
0 kommentar(er)
