Clock randomization is causing issues with template updates and VPN connections

I use Kicksecure as my sys-net template. For some time now, Kicksecure’s clock randomization has been increasingly causing problems. As I discussed on the Whonix forum, it initially caused 2FA failures due to time mismatches. At the same time, it began failing VPN connections because the VPN reported that the clock was not synced, and it also started throwing error messages during template updates.

For both VPN connections and template updates, success has become a matter of chance. Sometimes it works, and sometimes it doesn’t. Occasionally, I need to restart sys-net multiple times before the VPN connection works.

As I understand it, the clock randomization feature has been around for a long time. Why is it causing so many issues now? Is there any other solution to this problem besides disabling clock randomization or repeatedly trying until it works?

No relevant bootclockrandomization code/configuration changes in a long time.

Check sdwdate status/logs. Could be sdwdate failing or being inaccurate. Because sdwdate should result in a “randomized set accurate enough” clock.

If it’s not that, I don’t think any other work around apart those you know can be suggested.