This message was deleted.
# general
a
This message was deleted.
s
rancher/dashboard is the UI for rancher. Running it locally you will still need an instance of rancher to run against. This is set by supply the API arg
Copy code
API=your.rancher.domain yarn dev
w
~@stocky-account-63046 I did setup the
API=<our_kube_api>
in
.env
and I do see it showing up when I ran
yarn dev
But I still see the error and loading page in the UI.
Unknown Web socket upgrade request for /ws
Am I missing anything ? QQ? rancher/dashboard should just work with the
<kube backend api>
right ? or do we need to run rancher backend ?~
@stocky-account-63046 I did setup the
API=<our_kube_api>
in
.env
and I do see it showing up when I ran
yarn dev
But I still see the error and loading page in the UI.
Unknown Web socket upgrade request for /ws
Am I missing anything ? QQ? rancher/dashboard should just work with the
<kube backend api>
right ? or do we need to run rancher backend ? Thanks
s
as per the comment above, you need to point the ui of rancher (code from
rancher/dashboard
) at an instance of rancher
The
API
env value needs to be the address of that rancher instance, usually the domain name supplied when installing rancher. more generally it's the url you would normally use when accessing the UI built in to the rancher instance