Ziti Controller with Hostname yielded empty config yaml file

1

I wanted to use a FQDN, so I followed the instructions to customize the express install, but the controller won’t start. I realized the configuration yaml file is empty. Any thoughts?

ZITI_CONTROLLER_HOSTNAME=openziti..cloud;ZITI_EDGE_ROUTER_HOSTNAME=openziti..cloud; ZITI_EDGE_CONTROLLER_HOSTNAME=openziti..cloud;source ziti-cli-functions.sh; expressInstall

ubuntu@openziti-controller:~/.ziti/quickstart/openziti-controller$ ls -l
total 28
drwxrwxr-x 2 ubuntu ubuntu 4096 Dec 23 22:08 db
-rw-rw-r-- 1 ubuntu ubuntu 119 Dec 23 22:08 openziti-controller-init.log
-rw-rw-r-- 1 ubuntu ubuntu 4894 Dec 23 22:08 openziti-controller.env
-rw-rw-r-- 1 ubuntu ubuntu 119 Dec 23 22:08 openziti-controller.log
-rw-rw-r-- 1 ubuntu ubuntu 0 Dec 23 22:08 openziti-controller.yaml
drwxrwxr-x 2 ubuntu ubuntu 4096 Dec 23 22:08 pki
drwxrwxr-x 3 ubuntu ubuntu 4096 Dec 23 22:08 ziti-bin

And, the init log looks odd:
ubuntu@openziti-controller:~/.ziti/quickstart/openziti-controller$ cat openziti-controller-init.log
-bash: /home/ubuntu/.ziti/quickstart/openziti-controller/ziti-bin/ziti-null/ziti-controller: No such file or directory

2

I wonder if those two periods in your environment variables are causing a problem? Notice how there’s two periods?