ssh: Could not resolve hostname github.com + STATUS_ACCESS_VIOLATION at eip=68086014
From a few hours of struggling with installing git on Windows 7. First I installed the GitHub on Windows but not appealed to me. Then I installed the Git-1.9.2-preview20140411 and have started to have problems.
I suppose that there is a conflict by multiple installations. So I uninstalled everything. I decided to try Cygwin.
I acted according to this tutorial: How To install Git client on Windows using Cygwin By Johnathan Mark Smith
I added the generated public key SSH to my account on GittHub by Web browser . I created the first repository (through a browser).
After returning to the cygwin terminal and I typed:
git clone email@example.com:akawalko/ZFExt.git
I received such a result
Cloning into 'ZFExt'... ssh: Could not resolve hostname github.com: Non-recoverable failure in name resolution fatal: The remote end hung up unexpectedly
I do not understand this message. I did something wrong?
To the person who gave me the minus one. In your opinion I shouldn’t have asked. Instead, format the hard drive. In this way it would be okay?
I started to ask google with less detailed questions and i found it: git and ssh: Could not resolve hostname, ping works. I changed my DNS addresses to open DNS and was able to clone my repo by using ip adres instead domain:
git clone firstname.lastname@example.org:akawalko/ZFExt.git some_git_repo/
Using domain name still not work:
git clone email@example.com:akawalko/ZFExt.git some_git_repo/ Cloning into 'some_git_repo'... ssh: Could not resolve hostname github.com: Non-recoverable failure in name resolution fatal: The remote end hung up unexpectedly
Any ideas (other then changing DNS)?
7 Solutions collect form web for “ssh: Could not resolve hostname github.com + STATUS_ACCESS_VIOLATION at eip=68086014”
I had this issue inside a VMware Fusion VM. I had to change my network from NAT to Bridged and it started working.
For anyone else having this issue on VMWare Fusion and Windows 10, see this thread: https://communities.vmware.com/thread/518949?start=0&tstart=0
In summary, ssh won’t do dns resolution over NAT on Fusion with Windows 10. This is a known bug, but in the meantime, add an entry to your host file to access bitbucket
Also, as @Jim Redmond pointed out, bitbucket is changing their IP addresses soon (December 15, 2016).
Another, more permanent, option would be to set Google as your DNS provider. Use 220.127.116.11 or 18.104.22.168. Or for ipv6: 2001:4860:4860::8888 or 2001:4860:4860::8844. https://developers.google.com/speed/public-dns/docs/using
For me, it started happening when I upgraded to Git 2.7.4. The fix in the link below worked for me, you need to change SSH configuration in \etc\ssh\ssh_config.
See the last comment in the thread linked below:
Can’t resolve hostname with SSH
It’s been a few days and I have not found any solution. In conclusion, it’s more a problem with the operating system than the tools (Cygwin, Git).
I installed two competing Git clients (Git-1.9.2-preview20140411 and GitHub on Windows) which resulting in messed up windows registry. This gives in an error: STATUS_ACCESS_VIOLATION at eip=68086014. I returned to app GitHub For Windows and will use Windows Power Shell. It’s far from perfect but it works.
I was so focused on problem mentioned above that I didn’t spot problem with DNS. Because I don’t have knowledge how to solve this problem (answers on stackoverflow didn’t work for me) I will use the IP address instead of github domain in commands like git clone and others until I reinstall Windows. 🙁
I have modified the title to more precise.
Big thanks to @Chris for his contribution.
I had the same problem .then I tried with account name prefixed in the domain.
git clone firstname.lastname@example.org:akawalko/ZFExt.git
it worked for me also make sure in your git config you are using the same url.
Experienced the same problem with Windows 7 and VmWare Fusion 8.5.3.
Tried 2 options. Both worked. But issue is weird. Seem to happen to github.com and bitbucket.com only.
- Setting DNS manually in adapter settings (e.g. 22.214.171.124)
- Change networking from NAT to Bridged
For me it works fine when I changed the hostname to ip address.