Service troubleshooting
If traffic isn't flowing, scan logs for ERROR or WARN entries. Work from the edges toward the center of the network
in the order below.
Log review order
| Component | Focus | Key indicator of failure |
|---|---|---|
| 1. Client (Dial) | Interception & Enrollment | Service is not listed or shown as "intercepted." Check Service Policies. |
| 2. Host (Bind) | Offload & Connectivity | No incoming connection requests appear in logs. Check local app reachability. |
| 3. Controller | Routing & Circuits | Logs show routing failures or "no terminator" errors despite healthy edges. |
Common error reference
"No terminator"
- Symptoms: Client intercepts traffic, but the connection is reset/timed out; controller logs show
no terminator. - Causes: Missing
host.v1config, missing service router policy (SERP), or the hosting identity is offline.
Search the community
Search the OpenZiti Discourse for specific error strings or complex routing scenarios.