No existing binary found, creating the ZITI_BIN_DIR directory (/home/sysadmin/.ziti/quickstart/ztnctrl0101/ziti-bin/ziti-)
Downloading https://github.com/openziti/ziti/releases/download// to /home/sysadmin/.ziti/quickstart/ztnctrl0101/ziti-bin/ziti-/
tar: /home/sysadmin/.ziti/quickstart/ztnctrl0101/ziti-bin/ziti-/: Cannot read: Is a directory
tar: At beginning of tape, quitting now
tar: Error is not recoverable: exiting now
mv: cannot stat '/home/sysadmin/.ziti/quickstart/ztnctrl0101/ziti-bin/ziti-/ziti-extract/ziti': No such file or directory
rm: cannot remove '/home/sysadmin/.ziti/quickstart/ztnctrl0101/ziti-bin/ziti-/': Is a directory
chmod: cannot access '/home/sysadmin/.ziti/quickstart/ztnctrl0101/ziti-bin/ziti-/*': No such file or directory
OpenZiti binaries successfully extracted to /home/sysadmin/.ziti/quickstart/ztnctrl0101/ziti-bin/ziti-
/ziti-bin/ziti-/ is a strange error. It looks like something did not work properly. To me, it seems like you're hitting some bug that is probably going to be hard to diagnose. However, you don't need to use "getZiti". You can just download the latest binary onto the location of your ziti cli and then restart the processes.
I give this a try but didn't have any success. The services would fail to start after copying the new binary into the location.
Since my configuration is very simple I just opted to deploy a couple of new Ubuntu servers and re-install everything. I have a new controller and edge installed using the Host OpenZiti Anywhere express install all up and running. I noticed the ZAC console and the edge are using the same port 8441. How do I change the ZAC console port to use a different port so it's not going to be accessible from the Internet? In my previous installation this was using port 8443
You have two options. The "easy" option is to remove the ZAC binding and go back to the older style of deploying the ZAC in a standalone or docker-based deployment.
The better option is to split the management API away from the internet entirely, taking the ZAC along with it. It's certainly more important to have the management API off the internet than ZAC imo. The ZAC uses the management API to configure the overlay, it's a UI on top of that API. There are numerous forum posts on how to split the managment API as well as a video from a couple years back.