Getting Invalid Edge Controller for local quickstart

Ziti Administration Console
1

Hi, I followed the first service quickstart 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
ziti1251×1342 59.7 KB

2

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

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": {}
}
3

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.

4

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