# Uchiwa could connect to sensu go or it's obsolete? - SOLVED

**URL:** <https://discourse.sensu.io/t/uchiwa-could-connect-to-sensu-go-or-its-obsolete-solved/1063>\
**Category:** Sensu Go\
**Created:** [January 23, 2019, 8:02pm UTC](https://discourse.sensu.io/t/uchiwa-could-connect-to-sensu-go-or-its-obsolete-solved/1063 "2019-01-23T20:02:04Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![mogol](https://avatars.discourse-cdn.com/v4/letter/m/e56c9b/32.png) [@mogol](https://discourse.sensu.io/u/mogol)\
**Post date:** [January 23, 2019, 8:02pm UTC](https://discourse.sensu.io/t/uchiwa-could-connect-to-sensu-go-or-its-obsolete-solved/1063/1 "2019-01-23T20:02:04Z")

</div>

Hi,

I’m new in sensu, and I want to create my own playground. So I installed sensu go 5.1 (backend, agent and cli) on Ubuntu 18.04. Also I install uchiwa 1.5.0-1. All from official repository. I use a simpliest config. After run sensu, I could open Dashboard and see agent.

Also I could successfully connect to sensu api by SOAP UI based on token which generated by using cli tool. But when I try to run uchiwa, I get an a lot of errors, which said that 403 Not Authorized.

I am not sure if it’s a bug, or I missed something in documentation, or Uchiwa is obsolete because Dashboard exist…  
Below I put my uchiwa config.

```
{
  "sensu": [
    {
      "name": "Site",
      "host": "127.0.0.1",
      "port": 8080,
      "path": "/api/core/v2/namespaces/default",
      "user": "admin",
      "pass": "P@ssw0rd!",
      "timeout": 10
    }
  ],
  "uchiwa": {
    "host": "0.0.0.0",
    "port": 3001,
    "refresh": 10
  }
}

```

If someone could clarify why I couldn’t connect to sensu it’d be great.

Thanks and have a nice day

---

<div class="post-metadata">

**Author:** ![aaronsachs](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.sensu.io/aaronsachs/32/47_2.png) [@aaronsachs](https://discourse.sensu.io/u/aaronsachs)\
**Post date:** [January 23, 2019, 8:06pm UTC](https://discourse.sensu.io/t/uchiwa-could-connect-to-sensu-go-or-its-obsolete-solved/1063/2 "2019-01-23T20:06:26Z")

</div>

Hi @mogol,

Sensu Go now contains its own dashboard. Uchiwa will not work with Sensu Go, so you will not be able to use the two together.

---

<div class="post-metadata">

**Author:** ![mogol](https://avatars.discourse-cdn.com/v4/letter/m/e56c9b/32.png) [@mogol](https://discourse.sensu.io/u/mogol)\
**Post date:** [January 23, 2019, 8:08pm UTC](https://discourse.sensu.io/t/uchiwa-could-connect-to-sensu-go-or-its-obsolete-solved/1063/3 "2019-01-23T20:08:21Z")

</div>

Thanks a lot! 🙂

Maybe make sense to add this information to release\_notes of Sensu Go and / or Uchiwa to avoid similar confusion? Or I simply missed it?

---

<div class="post-metadata">

**Author:** ![aaronsachs](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.sensu.io/aaronsachs/32/47_2.png) [@aaronsachs](https://discourse.sensu.io/u/aaronsachs)\
**Post date:** [February 14, 2019, 1:57pm UTC](https://discourse.sensu.io/t/uchiwa-could-connect-to-sensu-go-or-its-obsolete-solved/1063/4 "2019-02-14T13:57:02Z")

</div>

Hi @mogol, you didn’t miss it. It’s not something that I believe we’ve addressed outright in our docs. I’ve [got a PR open](https://github.com/sensu/sensu-docs/pull/1204) to add this to the FAQ on the Sensu docs site so that this will be more clear.

---

<div class="post-metadata">

**Author:** ![aaronsachs](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.sensu.io/aaronsachs/32/47_2.png) [@aaronsachs](https://discourse.sensu.io/u/aaronsachs)\
**Post date:** [May 29, 2019, 3:44pm UTC](https://discourse.sensu.io/t/uchiwa-could-connect-to-sensu-go-or-its-obsolete-solved/1063/5 "2019-05-29T15:44:57Z")

</div>