<p>I'm trying to do a POC where I can use kubernetes with virtual switch connection type as Internal only. I managed to start minikube and cluster.</p>

<pre><code>PS C:\WINDOWS\system32&gt; minikube status
minikube: Running
cluster: Running
kubectl: Correctly Configured: pointing to minikube-vm at &lt;**Any random Ip**&gt;
</code></pre>

<p>but when I run <code>Minikube Dashboard</code> command I'm getting following error.</p>

<pre><code>PS C:\WINDOWS\system32&gt; minikube dashboard
Could not find finalized endpoint being pointed to by kubernetes-dashboard: Error validating service: Error getting serv
ice kubernetes-dashboard: Get https://&lt;**Same Ip as above**&gt;:8443/api/v1/namespaces/kube-system/services/kubernetes-dashboard:
Service Unavailable
</code></pre>

<p><strong>Following are the details</strong>:</p>

<pre><code>Driver : HyperV
OS : Windows 10
Dynamic Memory allocation : Disabled
Dynamic MAC allocation : Disabled
NATSwitch connection type : Internal Only
Minikube version : minikube-v0.25.1
Kubectl version : 1.9.0
</code></pre>

<p>(<strong>With external its work perfectly fine</strong> I need help with <strong>internal</strong> please refer the screenshot)</p>

<p>[<img src="https://i.stack.imgur.com/KbXAH.jpg" alt="Wi-fi property settings[1]">
<a href="https://i.stack.imgur.com/Ae16d.jpg" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/Ae16d.jpg" alt="HyperV virtual switch settings"></a></p>

<p>I found the solution for this particular issue and I would like to share with others.</p>

<p>The <strong>root cause</strong> of this issue was proxy settings our network administrator had set some proxy settings policy and that was preventing to access dashboard which was being exposed at <code>https://&lt;**Same Ip as above**&gt;:8443/api/v1/namespaces/kube-system/services/kubernetes-dashboard</code></p>

<p><strong>Solution</strong> for this is you need to check your proxy configuration and update them accordingly.</p>
