I have a run into an issue where certain cloud/VPS providers reserve or block ports for their own use Ex. 8443 (Plesk/HTTPS ALT)
This causes the ziti admin console to be unreachable as it runs on 8443. I was wondering if changing the ZAC port is trivial and which way, if any, would be the most efficient to specify an alternate port?
Any insight or advice would be appreciated.
Thanks!
After some additional reading I found that Zac is available on the management API port now, which essentially solves the port 8443 problem. I am still curious how one would go about changing ports in other circumstances if required.
Hi @bpsystems, welcome to the communitu and to OpenZiti!
Once it's configured, you can just change the configuration file for the controller and restart the process. Depending on how you installed the controller, you might have one port open or two. If your control plane port is different than the management plane then you'll be fine. If it's one port and thus the same port, you'll have to update any routers with the new control port. It's specified a few times in the controller config. Just find them all and change them to whatever port you wish.
The quickstart, the prod deployment guide and the config generation code all use the set of environment variables to emit a config file when you first install/generate it. You can find that list from the ziti cli: ziti create config environment or from github here
Thank you, that is what I've been looking for!