Agent-registry.json is suddently empty

zrok
21

These users are not able to run zrok. literally someone always need to come to their place.

I thought agent-remoting is more reliable. For now it is the case. Agent-remoting binding is always present.

I have noticed that frontend tokens are all different. Because one particular user creates a new one all the time he turns on his pc. He always unplug the cable first, then switch off his pc. Every day. It is a habit. So I remove the dead tokens using a script.

Now I wonder why zrok does not query the database to find the frontend tokens.

22

One has lost his agent-remoting binding. So zrok controller can not reach the agent.

{
  "file": "/__w/zrok/zrok/controller/agentRemoteStatus.go:48",
  "func": "github.com/openziti/zrok/controller.(*agentRemoteStatusHandler).Handle",
  "level": "error",
  "msg": "error retrieving remote agent status for 'zId' (domain.name): rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing: unable to dial service 'epdosdVKxuNQ' (dial failed: service 6CXUTsWwrxYqMOkZFM0kcu has no terminators)\"",
  "time": "2025-08-19T10:20:09.679Z"
}

The user has restarted his pc and the agent-remoting binding is back to life!

:grinning_face: