<p>I've seen this happen, especially on the newest (as of now) version. Try going into the "Infrastructure stack" and look for stopped containers. Often it helps to just refresh the entire deployment (hit the button "up to date" next to the "kubernetes" stack and hit save (If I remember correctly) in the bottom to force the "refresh").</p>

<p>You could also try manually just restarting the kubernetes-dashboard containers.</p>

<p>Lastly you could use the kubectl cli to delete the dashboard pods and force them to get recreated.</p>

<p>Let me know how it goes! I know I had to do this fix a few times.</p>

CC BY-SA 3.0
2017-08-23T11:20:15.730Z
Restarting the containers on DO worked, but the issue persists if Vagrant is used. The logs do not indicate why.
030
CC BY-SA 3.0
2017-08-20T22:58:54.380Z
2017-08-20T22:58:54.380Z
Trondh
<p>K8s has been created using rancher, but when one would like to access the UI it shows:</p>

<pre><code>Service unavailable
</code></pre>

<p><strong>Methods</strong></p>

<p><em>Method 1</em></p>

<ul>
<li>rancher was deployed locally using vagrant</li>
<li>k8s was deployed</li>
<li>click the ui button</li>
</ul>

<p><em>Method 2</em></p>

<p>perhaps the local firewall was causing the issue?</p>

<ul>
<li>rancher was deployed on digital ocean</li>
<li>k8s was deployed</li>
<li>service unavailable again</li>
</ul>

<rancher><kubernetes>
Why is the K8s UI not available when rancher is used?
030
# Why is the K8s UI not available when rancher is used?

(Asked by: username_0 on 2017-08-18)

K8s has been created using rancher, but when one would like to access the UI it shows:
Service unavailable

Methods
Method 1

rancher was deployed locally using vagrant
k8s was deployed
click the ui button

Method 2
perhaps the local firewall was causing the issue?

rancher was deployed on digital ocean
k8s was deployed
service unavailable again

**Tags:** rancher, kubernetes


---

## 1 answers

### Answer by username_1 on 2017-08-20. Score: 2 | Accepted answer

I've seen this happen, especially on the newest (as of now) version. Try going into the "Infrastructure stack" and look for stopped containers. Often it helps to just refresh the entire deployment (hit the button "up to date" next to the "kubernetes" stack and hit save (If I remember correctly) in the bottom to force the "refresh").

You could also try manually just restarting the kubernetes-dashboard containers.

Lastly you could use the kubectl cli to delete the dashboard pods and force them to get recreated.

Let me know how it goes! I know I had to do this fix a few times.

> **Comments:**
> **username_0**: Restarting the containers on DO worked, but the issue persists if Vagrant is used. The logs do not indicate why.  

---

