# Proxy / port forward to dashboard does not work

**URL:** <https://discuss.kubernetes.io/t/proxy-port-forward-to-dashboard-does-not-work/18444>\
**Category:** microk8s\
**Created:** [December 17, 2021, 4:58pm UTC](https://discuss.kubernetes.io/t/proxy-port-forward-to-dashboard-does-not-work/18444 "2021-12-17T16:58:20Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![jgfrm](https://avatars.discourse-cdn.com/v4/letter/j/49beb7/32.png) [@jgfrm](https://discuss.kubernetes.io/u/jgfrm)\
**Post date:** [December 17, 2021, 4:58pm UTC](https://discuss.kubernetes.io/t/proxy-port-forward-to-dashboard-does-not-work/18444/1 "2021-12-17T16:58:20Z")

</div>

Hi,

I installed microk8s as advertized at [Install a local Kubernetes with MicroK8s | Ubuntu](https://ubuntu.com/tutorials/install-a-local-kubernetes-with-microk8s).

Steps:  
sudo snap install microk8s --classic  
microk8s enable dashboard dns registry istio

```auto
microk8s kubectl port-forward -n kube-system service/kubernetes-dashboard 10443:443

```

results in

```auto
error: error upgrading connection: error dialing backend: dial tcp 172.10.16.12:10250: i/o timeout
(172.10.16.12 is the IP address from my host)

```

Using

```auto
microk8s dashboard-proxy

```

gives similar results.

Any ideas how to solve this?

Details:

cat /etc/os-release:  
NAME=“Ubuntu”  
VERSION=“20.04 LTS (Focal Fossa)”  
ID=ubuntu  
ID\_LIKE=debian  
PRETTY\_NAME=“Ubuntu 20.04 LTS”  
VERSION\_ID=“20.04”  
HOME\_URL=“[https://www.ubuntu.com/](https://www.ubuntu.com/)”  
SUPPORT\_URL=“[https://help.ubuntu.com/](https://help.ubuntu.com/)”  
BUG\_REPORT\_URL=“[Bugs : Ubuntu](https://bugs.launchpad.net/ubuntu/)”  
PRIVACY\_POLICY\_URL=“[Data privacy | Ubuntu](https://www.ubuntu.com/legal/terms-and-policies/privacy-policy)”  
VERSION\_CODENAME=focal  
UBUNTU\_CODENAME=focal

uname -a  
Linux ubuntu 5.4.0-91-generic #102-Ubuntu SMP Fri Nov 5 16:31:28 UTC 2021 x86\_64 x86\_64 x86\_64 GNU/Linux

snap list  
Name Version Rev Tracking Publisher Notes  
core18 20211028 2253 latest/stable canonical✓ base  
microk8s v1.22.4 2695 1.22/stable canonical✓ classic  
snapd 2.53.4 14295 latest/stable canonical✓ snapd

microk8s status  
microk8s is running  
high-availability: no  
datastore master nodes: 127.0.0.1:19001  
datastore standby nodes: none  
addons:  
enabled:  
dashboard # The Kubernetes dashboard  
dns # CoreDNS  
ha-cluster # Configure high availability on the current node  
istio # Core Istio service mesh services  
metrics-server # K8s Metrics Server for API access to service metrics  
registry # Private image registry exposed on localhost:32000  
storage # Storage class; allocates storage from host directory  
disabled:

---

<div class="post-metadata">

**Author:** ![mralexandrelise](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/mralexandrelise/32/18229_2.png) [@mralexandrelise](https://discuss.kubernetes.io/u/mralexandrelise)\
**Post date:** [May 6, 2026, 7:33pm UTC](https://discuss.kubernetes.io/t/proxy-port-forward-to-dashboard-does-not-work/18444/2 "2026-05-06T19:33:43Z")

</div>

Hey, I’m Alex

I’m new to k8s and I installed microk8s yesterday 2026-05-05 to try it out.

I stumbled upon the same issue than you for the dashboard and I followed these steps to investigate more and try to find the root cause of what seems to be the problem:

In your terminal try to do this:

1. 

```bash
sudo microk8s inspect  

```

This command allows you to have a complete report of the status of the system

2. You might find at the end of the resulting command hints to guide you to what to do next.

3. Stop then start microk8s `bash sudo microk8s stop && sudo microk8s start `

These steps might not fix the issue but might help you, like it did for me investigate further.

Hopefully it helps someone.

Have a delightful day Kubers!

---

<div class="post-metadata">

**Author:** ![mralexandrelise](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/mralexandrelise/32/18229_2.png) [@mralexandrelise](https://discuss.kubernetes.io/u/mralexandrelise)\
**Post date:** [May 6, 2026, 10:38pm UTC](https://discuss.kubernetes.io/t/proxy-port-forward-to-dashboard-does-not-work/18444/3 "2026-05-06T22:38:46Z")

</div>

A follow up to my previous reply. I saw that today it is advised to use headlamp instead of dashboard as a web ui for kubernetes. [GitHub - kubernetes-sigs/headlamp: A Kubernetes web UI that is fully-featured, user-friendly and extensible · GitHub](https://github.com/kubernetes-sigs/headlamp)

Just my 2cents

Hopefully it helps someone