Old version ControlR installation

[DimosRoump]

I have in my second PC an older version of ControlR and I have updated ControlR and now it does not work. I had read that if we update and the clients do not get the critical version then I will have problem. But I am at the case where the problem has happened. I tried uninstalling and reinstalling but it still does not work. Do you have any ideas what to do ,so I do not format the PC?

[bitbound]

@DimosRoump Moving this to Discussions since there weren't any reproduction steps or logs in the original issue that would indicate a code defect.

First, I'd check the agent logs to see if they indicate why it's failing to connect.

My guess is that the system clock is off where the agent is installed, and this is causing the signature verification in the new authentication mechanism to fail (which is by design to prevent replay attacks). If this is the case, it will be present in both the agent and server logs.

You can control the behavior with ControlR_AppOptions__AgentClockSkewTolerance env var in the compose file.

Check your compose file against the template on main to see if you're missing this configure key and/or any others. Link: https://github.com/bitbound/ControlR/blob/main/docker-compose/docker-compose.yml

If that's not the case, please share your agent logs so I can see if they reveal anything about the cause.