Visualizer shows errored state, but circuit works correctly

Ziti Administration Console
1

Hi team,
I'm really excited about this product and appreciate all the work that’s gone into it! I'm currently encountering a visual discrepancy in the Ziti Console that I’d like some help with.

In the Identity Service Path view for my homelab-service, the console displays:

  • homelab-router with a red (Errored) component status
  • The link from edge-router to homelab-router and the link from homelab-router to the service show as Errored

However, the service works perfectly — traffic flows from my device through the edge router and reaches the hosted service without issues.

  • The homelab-router is registered and online (ziti fabric list routers)
  • The fabric links are in Connected and up state (ziti fabric list links)
  • The service has an active terminator hosted on homelab-router
  • The circuit path correctly includes homelab-router and is in use
  • Policies (Dial/Bind) and configs (intercept.v1 and host.v1) are correctly applied
  • The Ziti Tunnel client on the iPhone is successfully connecting to the service

What I've verified:

  • No current errors in controller or router logs
  • All identities, services, policies, and routers are correctly configured
  • This visual state has remained even after restarts and refreshes

image
image2776×1626 445 KB

Is this a known issue or state sync problem in the Ziti Console (ZAC)?
Maybe I'm doing something wrong?

Thanks in advance!

2

Hi @shady2k, I'm happy to hear that you're enjoying OpenZiti so far!

Thanks for the detailed writeup, at a glance it looks like you are doing everything correctly.

While we dig in, please tell me the versions of the OpenZiti controller end Router you are running.

3

Of course! Controller/router: v1.5.4 ZAC: 3.12.2

4

Hi @shady2k

I'm experiencing the same issue with Controller v1.5.4 and ZAC v3.12.4. Everything is working fine otherwise, so it’s not a major concern for me—but it would be nice if it worked as expected.

I haven’t spent any time troubleshooting it yet, as this feature isn’t particularly important for my use case.