# Getting Invalid Edge Controller for local quickstart

**URL:** <https://openziti.discourse.group/t/getting-invalid-edge-controller-for-local-quickstart/885>\
**Category:** Ziti Administration Console\
**Created:** [November 23, 2022, 5:27pm UTC](https://openziti.discourse.group/t/getting-invalid-edge-controller-for-local-quickstart/885 "2022-11-23T17:27:38Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![andrewzah](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/andrewzah/32/634_2.png) [@andrewzah](https://openziti.discourse.group/u/andrewzah)\
**Post date:** [November 23, 2022, 5:27pm UTC](https://openziti.discourse.group/t/getting-invalid-edge-controller-for-local-quickstart/885/1 "2022-11-23T17:27:38Z")

</div>

Hi, I followed the [first service quickstart](https://github.com/openziti/ziti/blob/release-next/ziti/cmd/tutorial/tutorials/first-service.md) and I’m trying to connect with the ziti admin console locally.

Is there something else I need to do in order to get it to resolve correctly?

 ![ziti](https://global.discourse-cdn.com/free1/uploads/netfoundry/original/1X/38f675e0748d3f08917cf7ffa34c402b1997f067.jpeg)

---

<div class="post-metadata">

**Author:** ![smilindave26](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/smilindave26/32/185_2.png) [@smilindave26](https://openziti.discourse.group/u/smilindave26)\
**Post date:** [November 23, 2022, 6:01pm UTC](https://openziti.discourse.group/t/getting-invalid-edge-controller-for-local-quickstart/885/2 "2022-11-23T18:01:09Z")

</div>

What happens if you `curl` to that controller address? In my local setup, my controller is [https://localhost:1280](https://localhost:1280) (I see you are pointing to similar, but HTTP and not HTTPS), and I see:

```auto
dave$ curl -ks https://localhost:1280/version | jq .
{
  "data": {
    "apiVersions": {
      "edge": {
        "v1": {
          "apiBaseUrls": [
            "https://dave-lt.local:1280/edge/client/v1"
          ],
          "path": "/edge/client/v1"
        }
      },
      "edge-client": {
        "v1": {
          "apiBaseUrls": [
            "https://dave-lt.local:1280/edge/client/v1"
          ],
          "path": "/edge/client/v1"
        }
      },
      "edge-management": {
        "v1": {
          "apiBaseUrls": [
            "https://dave-lt.local:1280/edge/management/v1"
          ],
          "path": "/edge/management/v1"
        }
      }
    },
    "buildDate": "2022-11-10T14:39:47Z",
    "revision": "807dd591b1f5",
    "runtimeVersion": "go1.19.2",
    "version": "v0.26.11"
  },
  "meta": {}
}

```

---

<div class="post-metadata">

**Author:** ![TheLumberjack](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/thelumberjack/32/113_2.png) [@TheLumberjack](https://openziti.discourse.group/u/TheLumberjack)\
**Post date:** [November 23, 2022, 6:46pm UTC](https://openziti.discourse.group/t/getting-invalid-edge-controller-for-local-quickstart/885/3 "2022-11-23T18:46:12Z")

</div>

I’m 99% that it’s the http vs https issue. Ziti will never provide a non-https endpoint. ZAC can, but it’ll still contact the controller via https. Also the ZAC quickstart/install will show you how to setup ZAC for TLS.

---

<div class="post-metadata">

**Author:** ![andrewzah](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/andrewzah/32/634_2.png) [@andrewzah](https://openziti.discourse.group/u/andrewzah)\
**Post date:** [November 23, 2022, 6:58pm UTC](https://openziti.discourse.group/t/getting-invalid-edge-controller-for-local-quickstart/885/4 "2022-11-23T18:58:27Z")

</div>

It indeed was just http vs https. When I used https it worked flawlessly. Thanks all.