<p>I deploy a cluster (neo4j) with kubeadm based on <a href="https://github.com/neo4j-contrib/kubernetes-neo4j" rel="noreferrer">this</a> guide. Now I have these pods :</p>

<pre><code>NAME           READY   STATUS    RESTARTS   AGE
neo4j-core-0   1/1     Running   0          20h
neo4j-core-1   1/1     Running   0          20h
neo4j-core-2   1/1     Running   0          20h
</code></pre>

<p>and these services :</p>

<pre><code>NAME         TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)             AGE
kubernetes   ClusterIP   10.96.0.1        &lt;none&gt;        443/TCP             60d
neo4j        ClusterIP   None             &lt;none&gt;        7474/TCP,6362/TCP   20h
nginx        ClusterIP   None             &lt;none&gt;        80/TCP              25h
</code></pre>

<p>Then I install kubernetes dashboard :</p>

<pre><code>kubectl create -f https://raw.githubusercontent.com/kubernetes/dashboard/master/src/deploy/recommended/kubernetes-dashboard.yaml
</code></pre>

<p>So when I do <code>kubectl proxy</code> to access the dashboard, with below link, it says <strong><em>127.0.0.1 refused to connect</em></strong>.</p>

<p><code>http://localhost:8001/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/</code>.</p>

<p>What should I do to access the dashboard?</p>

<p>I also create sample user following <a href="https://github.com/kubernetes/dashboard/wiki/Creating-sample-user" rel="noreferrer">this</a> guide. </p>

Majid Rajabi
<p>Kubernetes dashboard fully rely on Apiserver. <code>Connection refused</code> means there is an issue with communication with apiserver. Please see <a href="https://github.com/kubernetes/dashboard/wiki/Accessing-Dashboard---1.7.X-and-above#kubectl-proxy" rel="noreferrer">https://github.com/kubernetes/dashboard/wiki/Accessing-Dashboard---1.7.X-and-above#kubectl-proxy</a></p>

<p>Also you can try to run </p>

<pre><code>kubectl proxy --address='0.0.0.0' --port=8002 --accept-hosts='.*'
</code></pre>

<p>And check if on other interface(port 8002) rather than <code>127.0.0.1</code> it works.</p>
