-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
error getting ssh client: No connection could be made because the target machine actively refused it. #2866
Comments
Are you running some kind of firewall? |
I have firewall enabled in my local. But I have 2 more VM's on hyper-v running with windows server image.. |
I have exactly the same issue on Win 10 Enterprise build 1709 and the latest minikube(0.27). |
after taking the help of admin dept found that I am getting same ip address for both host machine and minikube VM, they said that might be the issue and minikube doesnt have wifi resolving capability. So tried with LAN, surprisingly it worked. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
There are indeed some quirks around getting hyperv to a virtual switch on a wifi adapter: https://giritharan.com/configure-hyper-v-to-use-the-wireless-in-a-windows-10-computer/ |
@tstromberg Wireless does not have to be the problem. We are using this to great success with Minishift... so it is likely a different problem. (Note: especially as you refer to using a doc that uses an internal switch instead and NAT, which leads to other issues that need to be solved if using with Minikube as you can not do a static IP). Active refused most likely means it got blocked... and this can be local system policies if in a corporate environment, but also an application firewall (like antivirus). |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Same issue as everyone else. Has anyone found a resolution? |
I got this same error. I have a surface tablet / wifi all the time. I have an Ubuntu 18.04 server running in Hyper-V that I can access from other machines on my network so there's no general Hyper-V issue with wifi. First time trying minikube I got "connection actively refused" and it was trying 192.168.1.16. I suspected IP address conflict so I shutdown the minikube VM and 192.168.1.16 was still responding to pings. 192.168.1.16 was actually the IP assigned to my surface / the Hyper-V host. I started back up the minikube vm and used connect in the Hyper-V admin and confirmed the VM was also attempting to run on 192.168.1.16. So the "connection actively refused" was probably coming from my Surface itself. A little snooping in the file system and I found this file: C:\Users\gerry.minikube\machines\minikube\config.json With this content near the top: { All I had to do was add an IP address here that is within my network but outside my dhcp range so there's no chance of conflict. I used 192.168.1.102. That solved it for me at least -- minikube started with no issues after that. |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
@fejta-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Restarting the vEthernet "Switch" will make that DHCP assigns a new IP address and it won't be same. This worked for me. |
Any resolution of this? I keep getting Error dialing TCP: dial tcp 192.168.34.60:22: connectex: No connection could be made because the target machine actively refused it. I am starting the Minikube with the Hyper-v virtual switch on Windows 10 |
I believe this happens with the OOM killer runs. Because the kubernetes supervisor gets killed it doesn't restart, and often the SSH daemon is killed too. |
After switching to my wireless connection which is active ,I was connected to VPN and once I disconnected ( I stopped getting forbidden tcp socket messages and the error dialing TCP, of course I disabled ipv6) [stderr =====>] : [stderr =====>] : [stderr =====>] : [stderr =====>] : 10000 years later .... I0612 22:36:33.979541 51884 kubernetes.go:119] error getting Pods with label selector "k8s-app=kube-proxy" [Get https://192.168.0.103:8443/api/v1/namespaces/kube-system/pods?labelSelector=k8s-app%3Dkube-proxy: dial tcp 192.168.0.103:8443: connectex: No connection could be made because the target machine actively refused it.] I0612 22:37:05.570090 51884 round_trippers.go:408] Response Status: in 10017 milliseconds |
I am trying to set up minikube on windows10 pro 64bit and hyper-v
Downloaded minikube from here.
later trying to start using the following command
vSwitchKubernetes is an external vswitch created in hyper v.
I am unable to connect to minikube and getting the following errors
Tried different options like deleting minikube and starting again, disabling ipv6 etc..
VT support in bios is enabled.
Any suggestions on how to make it work would be greatly helpful.
Thanks..
The text was updated successfully, but these errors were encountered: