Maybe I don’t know what I’m talking about. To give exact detail, I set everything up according to the Zrok self-hosting guide. Self-Hosting Guide for Linux | NetFoundry Documentation .
As for the repeated timing, I believe I have a few of my zrok shares set to restart at 05:00 by systemd restarting (and it could be 10:00 as well because of time zone misconfiguration between machines). Sometimes with TCP services, the share goes “stale” and gets high ping and low throughput, restarting the zrok share service has been all needed to fix it.
Feb 18 05:00:01 MNZ-Zrok-2.5G ziti[1347]: {"file":"github.com/openziti/ziti/router/xgress_edge/hosted.go:472","func":"github.com/openziti/ziti/router/xgress_edge.(*hostedServiceRegistry).Remove","level":"info","msg":"terminator removed from router set","reason":"controller delete success","terminatorId":"3aeHdaT1glM6K7faT5na2k","time":"2026-02-18T05:00:01.663Z"}
Feb 18 10:00:02 MNZ-Zrok-2.5G ziti[1347]: {"file":"github.com/openziti/ziti/router/xgress_edge/hosted.go:472","func":"github.com/openziti/ziti/router/xgress_edge.(*hostedServiceRegistry).Remove","level":"info","msg":"terminator removed from router set","reason":"controller delete success","terminatorId":"7Vqxo9osYpJ2aRPsuRbptc","time":"2026-02-18T10:00:02.036Z"}
I do indeed see in the router logs the terminator removal at those times.
The downtime is an interesting point though. I’m sure that there is minimal downtime, but sometimes the services don’t recover for a few hours. I would be troubleshooting something else and a router would randomly decide to start functioning, and that’s the weirdness I’ve been dealing with. The shares which automatically restart are not the ones I’m tracking downtime issues with. As before mentioned, if the routers start having issues, then every share goes down.
I have probably 20 total net shares running at once, some TCP, some web.
At 10:00:02 the router logged that the existing terminator was closed:
updated state newState:3 oldState:2 reason:"channel closed"
terminatorId: 7Vqxo9osYpJ2aRPsuRbptc
terminator removed from router set (controller delete success)
Immediately (~900ms later), a new terminator was created and established:
establishing terminator
terminatorId: aMcYDSOdu9amVhkRdvkCA
sending create terminator v2 request
terminator established
About ~24 seconds later, a circuit attempt failed:
sending dial request to sdk
ERROR: cannot forward payload, no destination for circuit
closing while buffer contains unacked payloads
reported forwarding faults
circuit unrouted
Right now, I haven’t touched the routers or restarted anything and things are still working for the moment.