Zrok agent remoting : token is malformed

zrok
1

After restarting zrok-controller the error has disappeared. Then it appears again. I restart. Then the error appears again. I restart…..

Some times there are no errors at all in sys log but Zrok agent does not work : curl returns nothing.

zrok version v1.1.3

ziti version v1.6.7

{
  "file": "/__w/zrok/zrok/controller/agentPing.go:48",
  "func": "github.com/openziti/zrok/controller.(*agentPingHandler).Handle",
  "level": "error",
  "msg": "error retrieving agent version for 'zID' (name@domain): rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing: unable to dial service 'agent remoting token' (dial failed: token is malformed: token contains an invalid number of segments)\"",
  "time": "2025-08-23T07:36:47.958Z"
}

I have tried with version Zrok 1.1.2-1. After some time zrok agent remoting stops working. then it starts to work again. Then it stops. And so on.

Conclusion: Ziti 1.6.7 does not work with Zrok 1.1.2 & 1.1.3.

Everything becomes normal with ziti-router 1.5.4 and Zrok 1.1.2-1

There is another problem with zrok 1.1.3 : zrok-agent 1.1.3 access stops working suddenly.

{
  "_context": "ch{edge}->u{classic}->i{zId/NMp2}",
  "chSeq": 96,
  "connId": 9,
  "edgeSeq": 0,
  "error": "invalid api session id, expected 1ad4eb3a-72d7-4421-b879-651fa4b00466, got 2092ef26-98c3-40ee-885d-61372bf1f4f2",
  "file": "github.com/openziti/ziti/router/xgress_edge/listener.go:199",
  "func": "github.com/openziti/ziti/router/xgress_edge.(*edgeClientConn).processConnect",
  "level": "warning",
  "msg": "failed to dial fabric",
  "time": "2025-08-23T10:10:25.626Z",
  "token": "eyJhbGciO......"
}

 journalctl --since "12 hours ago" -g 'failed to dial fabric' | wc -l
3104

Zrok v1.1.2 works without this problem.