Unable to synchronize time

Hi! I updated Whonix today, and now I can’t synchronize the time. The host system, Kicksecure, also can’t synchronize the time.

ERROR: Time Synchronization Result:
systemcheck gave up waiting.

Time synchronization status: fail
sdwdate reports: Maximum allowed number of failures. Giving up.
whonix_firewall status: first run after boot
onion-time-pre-script reports:

__ ### START: ### /usr/libexec/helper-scripts/onion-time-pre-script
__ Status: First run after boot. (Creating file ‘/run/sdwdate/onion-time-script-after-boot’.)
__ Static Time Sanity Check: Within minimum time ‘Fri Oct 2 00:00:00 UTC 2026’ and expiration timestamp ‘Tue May 17 10:00:00 UTC 2033’, ok.
__ Tor Dormant Result: Unknown.
__ Tor circuit: established
__ Tor Consensus Time Sanity Check: The clock might be too fast. Clock is faster than consensus/valid-until 2026-11-03 10:00:00. extra guess: None.
__ Circuit confirmation (workstation): status/circuit-established = ‘1’.
__ Conclusion: Tor already reports circuit confirmed.
__ ### END: ### Exiting with exit_code ‘0’ indicating ‘success’.

Possible issues:

  • sdwdate time sources might be dysfunctional.

Recommendations:

A) Rerun systemcheck:

Start Menu - System - systemcheck

or in Terminal: systemcheck
or more verbose in Terminal: systemcheck --verbose --gui --cli

B) Restart sdwdate.

Start Menu - System - sdwdate-gui - right click on sdwdate-gui systray - Restart sdwdate

Or alternatively:
To fix, reboot into PERSISTENT Mode | SYSMAINT Session | system maintenance tasks, click “Open Terminal” in the System Maintenance Panel, and run:

sudo systemctl restart sdwdate

C) Manually set the time.

As last resort…

  1. Open a terminal. (Start Menu - System - Terminal)
  2. Use the manual clock setting tool.

sudo --set-home clock-random-manual-gui

3. Simulate sdwdate success.

sudo -u sdwdate touch /run/sdwdate/first_success

4. Rerun systemcheck.

INFO: System ready check (system) Result: OK.

INFO: System ready check (user) Result: OK.

INFO: AppArmor Check Result: OK.

INFO: Environment Variables Test Result: OK.

INFO: Account ‘user’ present in group ‘privleap’: Yes

INFO: Check ‘privleapd --check-config’ Result: OK.

INFO: Check ‘leaprun check-privleap’ Result: OK.

INFO: Check ‘leaprun check-privleap-environment-variables’ Result: OK.

INFO: Check ‘leaprun check-sudo’ Result: OK.

INFO: Whonix build version: 18.2.1.9

INFO: dist-general-cli: 37.8-1

INFO: derivative_major_release_version /etc/whonix_version: 18

INFO: Whonix Support Status of this Major Version: OK.

INFO: Check manual page (man) Result: OK.

INFO: Spectre Meltdown Test: skipping since spectre_meltdown_check=false, OK.

INFO: Package Manager Consistency Check Result: Output of command dpkg --audit was empty, OK.

INFO: systemd ‘system’ units check result: OK.

INFO: systemd ‘user’ units check result: OK.

INFO: systemd critical journal messages check result (current boot): OK.

INFO: systemd critical journal messages check result (previous boot): OK.

WARNING: systemd journal check result (current boot):
########################################
AVC apparmor=“DENIED” operation=“mknod” class=“file” profile=“/**/*-browser/Browser/firefox” name=“/run/user/1000/wayland-proxy-3200” comm=“firefox.real” requested_mask=“c” denied_mask=“c”
AVC apparmor=“DENIED” operation=“mknod” class=“file” profile=“/**/*-browser/Browser/firefox” name=“/run/user/1000/wayland-proxy-4240” comm=“firefox.real” requested_mask=“c” denied_mask=“c”
AVC apparmor=“DENIED” operation=“mknod” class=“file” profile=“/**/*-browser/Browser/firefox” name=“/run/user/1000/wayland-proxy-4701” comm=“firefox.real” requested_mask=“c” denied_mask=“c”
AVC apparmor=“DENIED” operation=“open” class=“file” profile=“/**/*-browser/Browser/firefox” name=“/proc/pressure/memory” comm=“firefox.real” requested_mask=“r” denied_mask=“r”
AVC apparmor=“DENIED” operation=“open” class=“file” profile=“/usr/libexec/kloak/find_wl_compositor” name=“/usr/share/locale/ru/LC_MESSAGES/kbd.mo” comm=“fgconsole” requested_mask=“r” denied_mask=“r”
Nov 03 12:16:56 host dracut-pre-pivot[475]: dmesg(1) may have more information after failed mount system call.
Nov 03 12:16:56 host dracut-pre-pivot[475]: mount: /sysroot: fsconfig() failed: ext4: Unknown parameter ‘nolock’.
Nov 03 12:19:59 host kernel: 12:19:59.584207 automount Error: vbsvcAutomounterMountIt: Failed to mount ‘111’ on ‘/media/sf_111’: Protocol error (-1,71)
Nov 03 12:20:00 host kernel: 12:20:00.590466 automount Error: vbsvcAutomounterMountIt: Failed to mount ‘111’ on ‘/media/sf_111’: Protocol error (-1,71)
Nov 03 12:20:50 host sdwdate[1692]: 2026-11-03 12:20:50 - sdwdate - ERROR - Maximum allowed number of failures. Giving up.

########################################
If you know what you are doing, feel free to disable this check. Create a file /etc/systemcheck.d/50_user.conf and add:

systemcheck_skip_functions+=" check_journal "

WARNING: systemd journal check result (previous boot):
########################################
AVC apparmor=“DENIED” operation=“mknod” class=“file” profile=“/**/*-browser/Browser/firefox” name=“/run/user/1000/wayland-proxy-3200” comm=“firefox.real” requested_mask=“c” denied_mask=“c”
AVC apparmor=“DENIED” operation=“mknod” class=“file” profile=“/**/*-browser/Browser/firefox” name=“/run/user/1000/wayland-proxy-4240” comm=“firefox.real” requested_mask=“c” denied_mask=“c”
AVC apparmor=“DENIED” operation=“mknod” class=“file” profile=“/**/*-browser/Browser/firefox” name=“/run/user/1000/wayland-proxy-4701” comm=“firefox.real” requested_mask=“c” denied_mask=“c”
AVC apparmor=“DENIED” operation=“open” class=“file” profile=“/**/*-browser/Browser/firefox” name=“/proc/pressure/memory” comm=“firefox.real” requested_mask=“r” denied_mask=“r”
AVC apparmor=“DENIED” operation=“open” class=“file” profile=“/usr/libexec/kloak/find_wl_compositor” name=“/usr/share/locale/ru/LC_MESSAGES/kbd.mo” comm=“fgconsole” requested_mask=“r” denied_mask=“r”
Oct 30 14:49:09 host kernel: 14:49:09.504495 automount Error: vbsvcAutomounterMountIt: Failed to mount ‘111’ on ‘/media/sf_111’: Protocol error (-1,71)
Oct 30 14:49:10 host kernel: 14:49:10.658774 automount Error: vbsvcAutomounterMountIt: Failed to mount ‘111’ on ‘/media/sf_111’: Protocol error (-1,71)
Oct 30 14:49:10 host kernel: vboxsf: SHFL_FN_MAP_FOLDER failed for ‘shared’: share not found

########################################
If you know what you are doing, feel free to disable this check. Create a file /etc/systemcheck.d/50_user.conf and add:

systemcheck_skip_functions+=" check_journal "

INFO: Network Interfaces Check Result: OK.

INFO: Qubes Settings Test Result: Skipped, because Qubes not detected.

INFO: Whonix firewall systemd unit check result: OK.

INFO: Check Package Manager Running Result: None running, OK.

INFO: Tor Check Result: Not running on Whonix-Gateway, OK.

INFO: Tor Config Check Result: OK.

INFO: Tor Running Check Result: Not running on Whonix-Gateway, therefore skipping, OK.

INFO: Tor SocksPort Reachability Test Result: Reachable. (curl exit code: 22 | curl status message: [22] - [HTTP page not retrieved. The requested url was not found or returned another error with the HTTP error code being 400 or above. This return code only appears if -f, --fail is used.])

ERROR: Time Synchronization Result:
systemcheck gave up waiting.

Time synchronization status: fail
sdwdate reports: Maximum allowed number of failures. Giving up.
whonix_firewall status: first run after boot
onion-time-pre-script reports:

__ ### START: ### /usr/libexec/helper-scripts/onion-time-pre-script
__ Status: First run after boot. (Creating file ‘/run/sdwdate/onion-time-script-after-boot’.)
__ Static Time Sanity Check: Within minimum time ‘Fri Oct 2 00:00:00 UTC 2026’ and expiration timestamp ‘Tue May 17 10:00:00 UTC 2033’, ok.
__ Tor Dormant Result: Unknown.
__ Tor circuit: established
__ Tor Consensus Time Sanity Check: The clock might be too fast. Clock is faster than consensus/valid-until 2026-11-03 10:00:00. extra guess: None.
__ Circuit confirmation (workstation): status/circuit-established = ‘1’.
__ Conclusion: Tor already reports circuit confirmed.
__ ### END: ### Exiting with exit_code ‘0’ indicating ‘success’.

Possible issues:

  • sdwdate time sources might be dysfunctional.

Recommendations:

A) Rerun systemcheck:

Start Menu - System - systemcheck

or in Terminal: systemcheck
or more verbose in Terminal: systemcheck --verbose --gui --cli

B) Restart sdwdate.

Start Menu - System - sdwdate-gui - right click on sdwdate-gui systray - Restart sdwdate

Or alternatively:
To fix, reboot into PERSISTENT Mode | SYSMAINT Session | system maintenance tasks, click “Open Terminal” in the System Maintenance Panel, and run:

sudo systemctl restart sdwdate

C) Manually set the time.

As last resort…

  1. Open a terminal. (Start Menu - System - Terminal)
  2. Use the manual clock setting tool.

sudo --set-home clock-random-manual-gui

3. Simulate sdwdate success.

sudo -u sdwdate touch /run/sdwdate/first_success

4. Rerun systemcheck.

This issue should be transient.

We’ll attempt to find a better solution as well.


Technical information:

My working theory is, that there are gaps in Tor consensus releases. At times, the Tor network is failing to produce a new Tor consensus. Quote collector.torproject.org/recent/relay-descriptors/consensuses/:

[TXT] 2026-11-03-01-00-00-consensus 2026-11-03 02:03  3.5M  
[TXT] 2026-11-03-02-00-00-consensus 2026-11-03 03:03  3.5M  
[TXT] 2026-11-03-03-00-00-consensus 2026-11-03 04:03  3.5M  
[TXT] 2026-11-03-04-00-00-consensus 2026-11-03 06:03  3.5M  
[TXT] 2026-11-03-06-00-00-consensus 2026-11-03 07:03  3.5M  
[TXT] 2026-11-03-07-00-00-consensus 2026-11-03 12:03  3.5M  
[TXT] 2026-11-03-11-00-00-consensus 2026-11-03 12:10  3.5M  

Numbers 8, 9, 10 are missing. That’s the gap.

sdwdate uses Tor consensus time as a sanity check to validate the time fetched from onions is sane. This fails when Tor consensus is stale (because the Tor network failed to produce it).

The solution would be to increase tolerance of Tor consensus release gaps.

Is it safe to use the system right now?

This generally cannot be nailed to a yes/no. → Security Overview

The messages shown by systemcheck are sufficient.

This case specifically isn’t a big deal. Related documentation:
Manually Set Clock Time and Date

Open Source projects typically come with legal disclaimers. (Whonix Copyright) And I am not aware of anyone giving any warranties. See also: About Computer Insecurity