Hi, After changing web browser (or cleaning the browser local storage), the ZAC do not works anymore: [image] So I declared the environment variable first in service.env which doesn't worked, in bootstrap.env and then hardcoded in entrypoint.bash because this is the script executed at the contro…

Okay now I see how it works. Since I have my controller behind a NAT, I have only one interface to listen to. So I changed the mgmt/fabric port on a port which is not exposed to the WAN, and accessible only with specific addresses: web: - name: client-management bindPoints: - interface…

I already saw this post and not resolved my issue openziti-console is already the newest version (3.9.1). my zac is 3.9+ and openziti hosted anywhere I tried ziti edge login, not working even after restarting ziti-controller.service

Are you saying you access your ZAC at $controller.url/zac and you still get this popup??? Can you try a private window? Would you be willing to share the url with me either here or DM? I haven't experienced this myself. Is there anything about your setup that you can share? Have you split the manag…

Yes exactly, zac running on a separate port of the API but on the same host. Private window also not working, sharing my URL by DM api management not split: web: - name: client-management bindPoints: - interface: 0.0.0.0:48440 address: hidden identity: ca: "…

[image] Damien: Yes exactly, zac running on a separate port of the API but on the same host. Ah. That makes sense as that will be what triggers this behavior. You're saying this configuration worked before? That confuses me. I would have expected you to receive an error. I would say you shou…

Oh you could also just put the ZAC on the same port as the management API. That will also fix this for you and let you stay on 3.9.x

This configuration worked properly when the local storage of my browser with all parameters was set. Once flushed, do not worked anymore. Downgraded to 3.9.0 and same problem, flushed local storage, tried in private window... root@openziti-controller:~# apt install openziti-console=3.9.0 Reading p…

Yes it was in this configuration in the past, but I do not want to make my ZAC internet facing for security reasons...

Ok, the other option is to also provide the managment API on the same "internal" port. The ZAC probes the same host:port, so you can either put zac on the public port, or host the management api on just the private port which sounds like what you were trying to do anyway. Move - binding: edg…

I want to make accessible the ZAC only through a ziti service or the LAN, how I configured it: - name: zac-console bindPoints: - interface: 0.0.0.0:48442 address: 192.168.X.X:48442 address: console.ziti:443 identity: ca: "pki/root/certs/root.cert" …

No Controllers Available

Ziti Administration Console

TheLumberjack February 16, 2025, 5:22pm 2

see Community Update: Adding controller URL's for NodeJS hosted ZAC instances

Topic		Replies	Views
Best practices of securing controller (and ZAC) Ziti Overlay	23	1009	March 8, 2023
Making ZAC dark Ziti Administration Console	37	1829	July 19, 2023
How to properly setup ZAC and management API General Questions	8	79	February 28, 2026
Dark ZAC with Management API on Localhost 18441 Ziti Administration Console	3	341	August 9, 2022
ZAC ports confusion Ziti Administration Console	4	96	February 13, 2025

No Controllers Available

Related topics