minikube: Unable to connect to the server: dial tcp 192.168.99.100:8443: i/o timeout
Problem statement and error:
After starting minikube on my mac, I cannot connect to the server using kubectl version.
minikube reports status is OK:
$ minikube status
minikube: Running
cluster: Running
kubectl: Correctly Configured: pointing to minikube-vm at 192.168.99.100
$ kubectl version
Client Version: version.Info{Major:“1”, Minor:“9”, GitVersion:“v1.9.3”, GitCommit:“d2835416544f298c919e2ead3be3d0864b52323b”, GitTreeState:“clean”, BuildDate:“2018-02-07T12:22:21Z”, GoVersion:“go1.9.2”, Compiler:“gc”, Platform:“darwin/amd64”}
Unable to connect to the server: dial tcp 192.168.99.100:8443: i/o timeout
Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT
Please provide the following details:
Environment:
Minikube version (use minikube version): v0.25.0
- OS (e.g. from /etc/os-release): MacOS High Sierra v. 10.13.2
- VM Driver (e.g.
cat ~/.minikube/machines/minikube/config.json | grep DriverName): “DriverName”: “virtualbox”, - ISO version (e.g.
cat ~/.minikube/machines/minikube/config.json | grep -i ISOorminikube ssh cat /etc/VERSION): “Boot2DockerURL”: “file:///Users/kdurston@us.ibm.com/.minikube/cache/iso/minikube-v0.25.1.iso”, - Install tools
N/A - Others:
$VBoxManage --version 5.1.14r112924
This is similar to closed #1224. Following suggestions in there, I tried the following without luck:
- disable firewall
- disable VPN
- restarted my machine
- reinstalled kubectl and minikube
What happened: $ kubectl cluster-info dump Unable to connect to the server: dial tcp 192.168.99.100:8443: i/o timeout $ kubectl version Client Version: version.Info{Major:“1”, Minor:“9”, GitVersion:“v1.9.3”, GitCommit:“d2835416544f298c919e2ead3be3d0864b52323b”, GitTreeState:“clean”, BuildDate:“2018-02-07T12:22:21Z”, GoVersion:“go1.9.2”, Compiler:“gc”, Platform:“darwin/amd64”} Unable to connect to the server: dial tcp 192.168.99.100:8443: i/o timeout $ kubectl cluster-info Kubernetes master is running at https://192.168.99.100:8443
What you expected to happen: I was hoping the command would be able to connect to the service.
How to reproduce it (as minimally and precisely as possible):
Output of minikube logs (if applicable):
Anything else do we need to know:
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Reactions: 10
- Comments: 22
‘minikube start’ solved it for me
I am pretty sure that this is due to untrusted certificate… try to connect to https://192.168.99.100:8443 with the browser… you will see…
now how to convince kubectl to trust this cert?
minikube delete --allafter deleting cluster and restarting it works for meWell… finally! I have found de problem with VirtualBox!! 🎊
It turns out that I had created the file “/etc/vbox/networks.conf” in order to include an specific network I wanted some time ago… That file specifies the networks allowed for “host-only networks”, so if you don’t have it, there are no limits, but if you have it… well now you see the problem.
Once I changed the name to “networks.conf.bak”, tried the next steps and it worked fine:
Cheers!
@manodupont I have the similar situation with you that it works if I turn off Cisco AnyConnect. I also need the VPN. I’m still trying to see how to resolve it. Anyway, your finding saved lots of research time for me. Thanks.
minikube start and reinstalling virtual box worked for me
So I just discovered that if I uninstall (not turning off), but uninstalling complement my VPN client (Cisco AnyConnect in my case), it ‘finally’ worked. After like a month of research. But still, this is not good. I DO need my VPN 😃.
So, is the driver will change anything compared to VBox you think ? Any warnings ?
On Jun 28, 2018, at 6:00 PM, Andrei Tchijov <notifications@github.commailto:notifications@github.com> wrote:
@manoduponthttps://github.com/manodupont have you tried minikube start --vm-driver hyperkit (you need to install hyperkit first)… in my case this option works the best.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/kubernetes/minikube/issues/2554#issuecomment-401085493, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AHN6oTZsyRgZG9SdNx03sJPnwNPGZqgUks5uBP2PgaJpZM4SHqYW.
Had a similar issue on my mac ( High Seirra ) . After re-installing virtualbox things started working. Did not have to restart the mac though, I still have my VMWare sitting there for now. Steps: