minikube: error getting ssh client: No connection could be made because the target machine actively refused it.

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

minikube start --vm-driver hyperv --hyperv-virtual-switch “vSwitchKubernetes”

vSwitchKubernetes is an external vswitch created in hyper v.

I am unable to connect to minikube and getting the following errors

minikube : E0601 15:41:56.250187   13560 start.go:159] Error starting host: Error creating host: Error executing step: Provisioning VM.
At line:1 char:1
+ minikube start --vm-driver hyperv --hyperv-virtual-switch "vSwitchKub ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (E0601 15:41:56....rovisioning VM.:String) [], RemoteException
    + FullyQualifiedErrorId : NativeCommandError
 
: Temporary Error: provisioning: error getting ssh client: Error dialing tcp via ssh client: dial tcp 172.16.49.99:22: connectex: No connection could be made 
because the target machine actively refused it.
Temporary Error: provisioning: error getting ssh client: Error dialing tcp via ssh client: dial tcp 172.16.49.99:22: connectex: No connection could be made 
because the target machine actively refused it.
Temporary Error: provisioning: error getting ssh client: Error dialing tcp via ssh client: dial tcp 172.16.49.99:22: connectex: No connection could be made 
because the target machine actively refused it.
Temporary Error: provisioning: error getting ssh client: Error dialing tcp via ssh client: dial tcp 172.16.49.99:22: connectex: No connection could be made 
because the target machine actively refused it.
Temporary Error: provisioning: error getting ssh client: Error dialing tcp via ssh client: dial tcp 172.16.49.99:22: connectex: No connection could be made 
because the target machine actively refused it..
 Retrying.
E0601 15:41:58.120926   13560 start.go:165] Error starting host:  Error creating host: Error executing step: Provisioning VM.
: Temporary Error: provisioning: error getting ssh client: Error dialing tcp via ssh client: dial tcp 172.16.49.99:22: connectex: No connection could be made 
because the target machine actively refused it.
Temporary Error: provisioning: error getting ssh client: Error dialing tcp via ssh client: dial tcp 172.16.49.99:22: connectex: No connection could be made 
because the target machine actively refused it.
Temporary Error: provisioning: error getting ssh client: Error dialing tcp via ssh client: dial tcp 172.16.49.99:22: connectex: No connection could be made 
because the target machine actively refused it.
Temporary Error: provisioning: error getting ssh client: Error dialing tcp via ssh client: dial tcp 172.16.49.99:22: connectex: No connection could be made 
because the target machine actively refused it.
Temporary Error: provisioning: error getting ssh client: Error dialing tcp via ssh client: dial tcp 172.16.49.99:22: connectex: No connection could be made 
because the target machine actively refused it.

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…

About this issue

Original URL
State: closed
Created 6 years ago
Comments: 16 (4 by maintainers)

Most upvoted comments

@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).

gbraad on Sep 19, 2018

Restarting the vEthernet “Switch” will make that DHCP assigns a new IP address and it won’t be same. This worked for me.

epgeroy on Jan 6, 2019

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. Now I get different IP address for host and VM.

pmaheshgupta on Jun 12, 2018