Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Unable to connect to the server: dial tcp [::1]:8080: connectex: No connection could be made because the target machine actively refused it. Windows 10 #53881
I want to learn Kubernetes and installed it on my laptop that is running Windows 10.
Install went fine. In the firewall Exception list, I have put minikube and kubectl.
I am getting below error
Unable to connect to the server: dial tcp [::1]:8080: connectex: No connection could be made because the target machine actively refused it.
What could be possible reason for this error? How to fix it?
Please let me know what all information you need to help me on this. I searched for other similar issues but that did not help much.
Thank you in advance.
This doesn't look related to running Kubernetes on Windows, but getting Minikube running inside a VM on Windows. This should probably be closed in favor of creating a new question on Stack Overflow, or finding one that is already answered.
A number of related troubleshooting issues exist: https://stackoverflow.com/search?q=%5Bminikube%5D+windows
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.
I looked a bit further into my issue, and it turned out that I had a different issue of kubectl not being properly configured with a kubeconfig that points to an actually running API server.
@Dev1969 - there could be many issues that could be causing this issue for you, including the api server not running, kubectl on your windows machine not being configured correctly, and that's on top of networking issues in your VirtualBox setup. Without further details (logs , etc) it would not be possible to further diagnose this issue. As previously mentioned, this is unlikely to be windows (or sig-windows) related.
With that, it does seem like this issue should be closed . @michmike - can you please close this issue to reduce clutter ?