For both 2.0b6 and 2.0b7, when you type http://127.0.0.1:4200/ in your browser, it will direct the url to http://127.0.0.1:4200/runs And then click around for runs, flows and deployments side menus, all work fine. But when you refresh the page with any addresses: http://127.0.0.1:4200/runs http://127.0.0.1:4200/flows http://127.0.0.1:4200/deployments it will return the following json:

{
  "detail": "Not Found"
}

This issue is known and actively being worked on 🙂

Thanks.

Thank you for letting us know. This is a known issue. We are fixing it. You can get back to http://127.0.0.1:4200/runs by going to http://127.0.0.1:4200 first then clicking the section you want to access

Any way you can enable API keys for local server like the one in your cloud?

We historically don’t provide auth for the open source version because it takes a lot of effort to make the service performant and integrate with other tools.

Thanks.

We do have users that have some form of auth, like password protecting the UI (UI is not yet open source but will be)

That is for version 1 only? not in version 2 yet?

Yeah