That’s what I expect, yeah. To be honest, I would probably recommend you re-run the quickstart and make sure you use an address that will be routable by any/all clients on your network just to make sure it won’t be a problem.
You can do that by running (i was typing this up when your next response came in):
# source the helper script...
source /dev/stdin <<< "$(wget -qO- https://get.openziti.io/quick/ziti-cli-functions.sh)";
# unset any env vars already set
unsetZitiEnv
# set the hostname you want the controller to be known at -- must be addressable by any client looking to use the network
export ZITI_EDGE_CONTROLLER_HOSTNAME="${EXTERNAL_DNS}"
# set the hostname for the edge router
export ZITI_EDGE_ROUTER_HOSTNAME="${EXTERNAL_DNS}"
I don’t think that log message is entirely accurate, maybe. I think you’re better off by first making sure you setup an overlay that will work for you. You could probably test that theory by going to a browser and trying to access the HTTP api of the controller, which for you should be at https://ziti:1280