# Dashboard returning forbidden after following tutorial

**URL:** <https://forums.suse.com/t/dashboard-returning-forbidden-after-following-tutorial/17134>\
**Category:** k3s, k3OS, and k3d\
**Created:** [April 12, 2020, 8:08am UTC](https://forums.suse.com/t/dashboard-returning-forbidden-after-following-tutorial/17134 "2020-04-12T08:08:12Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![apoz](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/apoz/32/6274_2.png) [@apoz](https://forums.suse.com/u/apoz)\
**Post date:** [April 12, 2020, 8:08am UTC](https://forums.suse.com/t/dashboard-returning-forbidden-after-following-tutorial/17134/1 "2020-04-12T08:08:12Z")

</div>

Hi all,

I’m following the tutorial here: [https://rancher.com/docs/k3s/latest/en/installation/kube-dashboard/](https://rancher.com/docs/k3s/latest/en/installation/kube-dashboard/) (in some Ubuntu 20.04 VM).

I follow all the steps in the tutorial to set up the dashboard, but after setting up the proxy (on the IP address of the machine with sudo k3s kubectl proxy --address 192.168.4.39), I am not able to connect to it.

All I’ve got is ‘forbidden’ as response.

> curl [http://192.168.4.39:8001/api/v1/namespaces/kubernetes-dashboard/services/https:kubernetes-dashboard:/proxy/](http://192.168.4.39:8001/api/v1/namespaces/kubernetes-dashboard/services/https:kubernetes-dashboard:/proxy/)   
> -H “Accept: application/json”   
> -H “Authorization: Bearer ${AUTHENTICATION\_TOKEN}”  
> Forbidden

Am I missing something? Is there any log I can check to see what’s going on?

Many thanks,  
Andres

---

<div class="post-metadata">

**Author:** ![apoz](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/apoz/32/6274_2.png) [@apoz](https://forums.suse.com/u/apoz)\
**Post date:** [April 14, 2020, 6:39am UTC](https://forums.suse.com/t/dashboard-returning-forbidden-after-following-tutorial/17134/2 "2020-04-14T06:39:47Z")

</div>

The problem I was having we that i was trying to access the dashboard from a remote IP.

Just changing the type of the kubernetes-dashboard service from clusterIP to NodePort made it available.

Cheers
