Today i installed Openziti quick start and then tried to install Console on same Ubuntu machine. How installation process is changed like what it was before. (had to install the npm, build the ng)
Now it is very simple but still not able to get the GUI page. I installed the controller and console on azure VM ubuntu machine.
Anyone can help me out on this?
Hi @wahmad, yes the install is much easier now 
When you say you can't access the console, could you share the url to the controller (either publicly or via private DM to me). Can you confirm what your controller's config file looks like? you have something like this, right?
apis:
...
...
- binding: zac
options:
location: /home/ubuntu/.ziti/quickstart/ip-172-31-11-231/zacs/v3.1.0
assuming you do, does index.html exist at that folder? for example
ls -l /home/ubuntu/.ziti/quickstart/ip-172-31-11-231/zacs/v3.1.0
total 46852
drwxr-xr-x 16 ubuntu ubuntu 4096 Apr 10 20:21 assets
-rw-r--r-- 1 ubuntu ubuntu 10355 Apr 10 20:21 color.png
-rw-r--r-- 1 ubuntu ubuntu 948 Apr 10 20:21 favicon.ico
-rw-r--r-- 1 ubuntu ubuntu 293 Apr 10 20:21 hue.png
-rw-r--r-- 1 ubuntu ubuntu 7374 Apr 10 20:21 index.html
-rw-r--r-- 1 ubuntu ubuntu 624996 Apr 10 20:21 lottie-web.js
-rw-r--r-- 1 ubuntu ubuntu 1438640 Apr 10 20:21 lottie-web.js.map
-rw-r--r-- 1 ubuntu ubuntu 3120170 Apr 10 20:21 main.js
-rw-r--r-- 1 ubuntu ubuntu 1247441 Apr 10 20:21 main.js.map
-rw-r--r-- 1 ubuntu ubuntu 106656 Apr 10 20:21 polyfills.js
-rw-r--r-- 1 ubuntu ubuntu 221466 Apr 10 20:21 polyfills.js.map
-rw-r--r-- 1 ubuntu ubuntu 72380 Apr 10 20:21 primeicons.eot
-rw-r--r-- 1 ubuntu ubuntu 291454 Apr 10 20:21 primeicons.svg
-rw-r--r-- 1 ubuntu ubuntu 72204 Apr 10 20:21 primeicons.ttf
-rw-r--r-- 1 ubuntu ubuntu 72280 Apr 10 20:21 primeicons.woff
-rw-r--r-- 1 ubuntu ubuntu 30180 Apr 10 20:21 primeicons.woff2
-rw-r--r-- 1 ubuntu ubuntu 14795 Apr 10 20:21 runtime.js
-rw-r--r-- 1 ubuntu ubuntu 13076 Apr 10 20:21 runtime.js.map
-rw-r--r-- 1 ubuntu ubuntu 565570 Apr 10 20:21 styles.css
-rw-r--r-- 1 ubuntu ubuntu 724693 Apr 10 20:21 styles.css.map
-rw-r--r-- 1 ubuntu ubuntu 12296794 Apr 10 20:21 vendor.js
-rw-r--r-- 1 ubuntu ubuntu 26992253 Apr 10 20:21 vendor.js.map
the configuration is incorrect.
find the full, absolute path for ~/.ziti/quickstart/Openziti-controller/zac and update your 'location' with that value and restart the controller and it'll work. It should be /home/ubuntu/.ziti/quickstart/Openziti-controller/zac based on your ls command shown above.
The zac is now delivered on the port that the management API is exposed at so that it does not have CORS-issues.
https://controller-vt.usgovarizona.cloudapp.usgovcloudapi.net:8441/zac/login
Yeah by doing this it is working.
Q : Is this new way to login the console or it is happened because of wrong configuration in my controller ?
Both things are true. You had used the wrong path in the config (pointing to the root folder for zac) and you were accessing the old port (8443).
So still we need to allow the port 8443 or we can deny it in our FW policy ?
With this deployment pattern, it's not needed. You just need to enable whatever port is configured for your management api.
Ok, Thank you very much for your quick support.