Sometimes it may be your company firewall. If you happen to run into any of the errors above in GitKraken, before you make any changes, check your connectivity first. Daily Git actions, like push, pull, fetch, and setting upstream are easier with GitKraken, thanks to the incredible visual context offered by the central. Alternatively, you can drag-and-drop a branch from the central graph in GitKraken to push instead of setting upstream. In the world of IT, there are many layers at work (think OSI Model) to ensure connectivity. Right-click on a branch to set the upstream or click the ellipsis icon. After that, we could ping successfully and everything we asked GitKraken to do worked as expected. It turned out that their ISP had issues with their DNS servers and forced a reconnect on their router once those DNS servers were fixed. After a few minutes they returned to the call. Changing DNS servers should have that kind of impact. Once they did that, they vanished off the virtual call, and I felt a moment of concern. We tried to fix that by changing their DNS Servers to OpenDNS. Same problem.Ĭonsidering we were having a virtual meeting that seemed odd as they were connected to the internet, but it seemed like their DNS servers were having issues. I then had them test to see if they could ping. For some reason their system could not resolve the hostname. I then had them see if they could ping from their dev environment. Everything on their status page reported as normal, and again everyone else on the team could push/pull/create/clone/etc. Obviously the first thing was to look at the status page for GitHub as there have been times when GitHub has various systems attacked. Considering this was the second time for this particular client, I figured I needed to look deeper. Usually when running into an error when working with an application, the tendency is to land the error squarely on the shoulders of the app failing in some way. This time however, I decided to dig a bit deeper. Again, I reached out to some fellow GK Ambassadors to discuss the issue. I had a hard time believing that this instance had corrupted as well, even though it was the same client's team member. Then, two weeks ago, we ran into the same issue. Nothing had changed on their system during this time except for us making changes to the code in the project they were working on.Īfter some deliberation with other amazing GitKraken Ambassadors, we figured out that the GK install was probably corrupt, so we fully deleted and reinstalled it on that team member's system. The repos were there, could be accessed by others on the team, but this one individual. We checked to make sure GitHub wasn't running into one of their occasional issues. There are a lot of different articles out there suggesting fixes for this specific issue including checking the firewall or using https instead of ssh, but everything had been fine until just that moment.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |