Whonix on Mac M1 (ARM) - User Support (still unsupported at time of writing)

Unsupported Platforms
352

Probably outdated tb-updater package version.

Your image was probably created without --repo true, so without Kicksecure and without Whonix repository, so you’re not getting updates.

Solution:

Either A) update tb-udpater from source code or B) update from distribution repository.

1. Enable the repository with the following command or by reading Whonix ™ APT Repository.

sudo repository-dist --enable --repository stable

2. Update according to the usual documentation. (Operating System Software and Updates) (Whonix is based on Kicksecure.)

3. Done.

Might be fixed.

354

Outdated.

translation:
“Please send me malware.”

Bad idea inviting strangers sending binaries.

355

Note:

356

Took a while to figure it out, so I’ll share for anyone who might find it useful.

On Debian 11, the trick was to install the fpc-3.2.2 package (free Pascal compiler) from the Debian backports repo, instead of version 3.2.0 (fp-compiler-3.2.0) that is installed with the build. The backports repo was added as explained in https://backports.debian.org/Instructions/, and then apt install fpc/bullseye-backports. After this, building worked using these commands (thanks to @moonme):

git clone --jobs=4 --recurse-submodules https://github.com/Whonix/derivative-maker.git

cd derivative-maker && git checkout --recurse-submodules 16.1.1.5-stable

~/derivative-maker/derivative-maker --flavor whonix-gateway-xfce --target utm --arch arm64 --build --tb open

~/derivative-maker/derivative-maker --flavor whonix-workstation-xfce --target utm --arch arm64 --build --tb open

After these steps, ~/derivative-binary/16.1.1.5/ contained the .tar.gz archives.

357

Why use Debian 11 / bullseye and Whonix 16 if both are already oldstable, meaning not the latest stable?

358

Um, mostly because I followed the macOS Wiki that said to download Debian bullseye :sweat_smile:

I actually tried to build Whonix 17 on Debian 12, but the build failed after some time, so I wasn’t sure if I should wait for a “stable” tag before trying stuff out…

359

Anyway, tried it again after your message, building tag 17.0.4.0 worked, so thanks!

360

Whonix ™ VM Build Documentation chapter Choose Version in Whonix wiki

1 Like
361

Is there anyway to make the sparse file normal size?

362

Convert sparse to non-sparse? Possible but then you’d waste space. Why would you want this?

What’s normal size?

What’s the issue you trying to solve?

related:

363

I’m trying to convert the whonix gateway and whonix workstation utm file which is 107gb each atm to a non-sparse utm file so I can store it in my hard drive on the MacBook instead of a sd card. So I can utilise the FDE. With the current form of the utm images it takes up all of the space on the hardrive. I only have 256gb. So when I put the images on hardrive all the space is taken up. When I followed the build guide, after it finished the files were 107gb. I know that they are usually much much less, 1-2Gb or something like that.

What can I do to resolve this issue.

The normal size of the whonix images I meant, for example on a virtual box download the images are small.

Does this make sense?

I need to convert whonix utm images from their apparent size of 107g to the real size, so I can store it on my hard drive

364

Try to find some Mac support who can tell you how to use sparse files or some image format on Mac that supports sparse files.

365

Build command append for 25 GB size:

--vmsize 25G

Or some other number.

366

Thanks for this, this has solved the problem, i have another problem with whonix gateway, everytime i reboot the vm the time is off i have to manually fix it every time.

So boot then run system check and get this error


[gateway user ~]% systemcheck
[INFO] [systemcheck] Tor Connection Result:
- Connecting for 0 seconds. | 100 % done. 
- Tor Circuit: established.
- Tor reports: NOTICE BOOTSTRAP PROGRESS=100 TAG=done SUMMARY="Done"
- Timesync status: not done.
- sdwdate reports: Preparation not done yet. More more information,             see: sdwdate-gui -> right click -> Open sdwdate's log
- onion-time-pre-script reports: 
__ ### START: ### /usr/libexec/helper-scripts/onion-time-pre-script
__ Status: Subsequent run after boot.
__ Static Time Sanity Check: Within minimum time 'Mon Jun 12 00:00:00 UTC 2023' and expiration timestamp 'Tue May 17 10:00:00 UTC 2033', ok.
__ Tor reports: NOTICE BOOTSTRAP PROGRESS=100 TAG=done SUMMARY="Done"
__ Tor circuit: established
__ Tor Consensus Time Sanity Check: The clock might be too fast. Clock is faster than consensus/valid-until 2023-09-10 14:00:00. extra guess: Tor consensus might be outdated and download might still be in progress since this is the first run after boot.
__ anondate_use: Running 'anondate-set' (by creating file '/run/sdwdate/request_anondate-set')...
__ ### END: ### Exiting with exit_code '2' indicating 'wait, show busy icon and retry.'.
[INFO] [systemcheck] Tor Connection Result:
- Connecting for 2 seconds. | 100 % done. 
- Tor Circuit: established.
- Tor reports: NOTICE BOOTSTRAP PROGRESS=100 TAG=done SUMMARY="Done"
- Timesync status: not done.
- sdwdate reports: Preparation not done yet. More more information,             see: sdwdate-gui -> right click -> Open sdwdate's log
- onion-time-pre-script reports: 
__ ### START: ### /usr/libexec/helper-scripts/onion-time-pre-script
__ Status: Subsequent run after boot.
__ Static Time Sanity Check: Within minimum time 'Mon Jun 12 00:00:00 UTC 2023' and expiration timestamp 'Tue May 17 10:00:00 UTC 2033', ok.
__ Tor reports: NOTICE BOOTSTRAP PROGRESS=100 TAG=done SUMMARY="Done"
__ Tor circuit: established
__ Tor Consensus Time Sanity Check: The clock might be too fast. Clock is faster than consensus/valid-until 2023-09-10 14:00:00. extra guess: Tor consensus might be outdated and download might still be in progress since this is the first run after boot.
__ anondate_use: Running 'anondate-set' (by creating file '/run/sdwdate/request_anondate-set')...
__ ### END: ### Exiting with exit_code '2' indicating 'wait, show busy icon and retry.'.
[INFO] [systemcheck] Tor Connection Result:
- Connecting for 4 seconds. | 100 % done. 
- Tor Circuit: established.
- Tor reports: NOTICE BOOTSTRAP PROGRESS=100 TAG=done SUMMARY="Done"
- Timesync status: not done.
- sdwdate reports: Preparation not done yet. More more information,             see: sdwdate-gui -> right click -> Open sdwdate's log
- onion-time-pre-script reports: 
__ ### START: ### /usr/libexec/helper-scripts/onion-time-pre-script
__ Status: Subsequent run after boot.
__ Static Time Sanity Check: Within minimum time 'Mon Jun 12 00:00:00 UTC 2023' and expiration timestamp 'Tue May 17 10:00:00 UTC 2033', ok.
__ Tor reports: NOTICE BOOTSTRAP PROGRESS=100 TAG=done SUMMARY="Done"
__ Tor circuit: established
__ Tor Consensus Time Sanity Check: The clock might be too fast. Clock is faster than consensus/valid-until 2023-09-10 14:00:00. extra guess: Tor consensus might be outdated and download might still be in progress since this is the first run after boot.
__ anondate_use: Running 'anondate-set' (by creating file '/run/sdwdate/request_anondate-set')...
__ ### END: ### Exiting with exit_code '2' indicating 'wait, show busy icon and retry.'.
[INFO] [systemcheck] Tor Connection Result:
- Connecting for 6 seconds. | 100 % done. 
- Tor Circuit: established.
- Tor reports: NOTICE BOOTSTRAP PROGRESS=100 TAG=done SUMMARY="Done"
- Timesync status: not done.
- sdwdate reports: Preparation not done yet. More more information,             see: sdwdate-gui -> right click -> Open sdwdate's log
- onion-time-pre-script reports: 
__ ### START: ### /usr/libexec/helper-scripts/onion-time-pre-script
__ Status: Subsequent run after boot.
__ Static Time Sanity Check: Within minimum time 'Mon Jun 12 00:00:00 UTC 2023' and expiration timestamp 'Tue May 17 10:00:00 UTC 2033', ok.
__ Tor reports: NOTICE BOOTSTRAP PROGRESS=100 TAG=done SUMMARY="Done"
__ Tor circuit: established
__ Tor Consensus Time Sanity Check: The clock might be too fast. Clock is faster than consensus/valid-until 2023-09-10 14:00:00. extra guess: Tor consensus might be outdated and download might still be in progress since this is the first run after boot.
__ anondate_use: Running 'anondate-set' (by creating file '/run/sdwdate/request_anondate-set')...
__ ### END: ### Exiting with exit_code '2' indicating 'wait, show busy icon and retry.'.
[INFO] [systemcheck] Tor Connection Result:
- Connecting for 8 seconds. | 100 % done. 
- Tor Circuit: established.
- Tor reports: NOTICE BOOTSTRAP PROGRESS=100 TAG=done SUMMARY="Done"
- Timesync status: not done.
- sdwdate reports: Preparation not done yet. More more information,             see: sdwdate-gui -> right click -> Open sdwdate's log
- onion-time-pre-script reports: 
__ ### START: ### /usr/libexec/helper-scripts/onion-time-pre-script
__ Status: Subsequent run after boot.
__ Static Time Sanity Check: Within minimum time 'Mon Jun 12 00:00:00 UTC 2023' and expiration timestamp 'Tue May 17 10:00:00 UTC 2033', ok.
__ Tor reports: NOTICE BOOTSTRAP PROGRESS=100 TAG=done SUMMARY="Done"
__ Tor circuit: established
__ Tor Consensus Time Sanity Check: The clock might be too fast. Clock is faster than consensus/valid-until 2023-09-10 14:00:00. extra guess: Tor consensus might be outdated and download might still be in progress since this is the first run after boot.
__ anondate_use: Running 'anondate-set' (by creating file '/run/sdwdate/request_anondate-set')...
__ ### END: ### Exiting with exit_code '2' indicating 'wait, show busy icon and retry.'.
[INFO] [systemcheck] Tor Connection Result:
- Connecting for 10 seconds. | 100 % done. 
- Tor Circuit: established.
- Tor reports: NOTICE BOOTSTRAP PROGRESS=100 TAG=done SUMMARY="Done"
- Timesync status: not done.
- sdwdate reports: Preparation not done yet. More more information,             see: sdwdate-gui -> right click -> Open sdwdate's log
- onion-time-pre-script reports: 
__ ### START: ### /usr/libexec/helper-scripts/onion-time-pre-script
__ Status: Subsequent run after boot.
__ Static Time Sanity Check: Within minimum time 'Mon Jun 12 00:00:00 UTC 2023' and expiration timestamp 'Tue May 17 10:00:00 UTC 2033', ok.
__ Tor reports: NOTICE BOOTSTRAP PROGRESS=100 TAG=done SUMMARY="Done"
__ Tor circuit: established
__ Tor Consensus Time Sanity Check: The clock might be too fast. Clock is faster than consensus/valid-until 2023-09-10 14:00:00. extra guess: Tor consensus might be outdated and download might still be in progress since this is the first run after boot.
__ anondate_use: Running 'anondate-set' (by creating file '/run/sdwdate/request_anondate-set')...
__ ### END: ### Exiting with exit_code '2' indicating 'wait, show busy icon and retry.'.
[INFO] [systemcheck] Tor Connection Result:
- Connecting for 12 seconds. | 100 % done. 
- Tor Circuit: established.
- Tor reports: NOTICE BOOTSTRAP PROGRESS=100 TAG=done SUMMARY="Done"
- Timesync status: not done.
- sdwdate reports: Preparation not done yet. More more information,             see: sdwdate-gui -> right click -> Open sdwdate's log
- onion-time-pre-script reports: 
__ ### START: ### /usr/libexec/helper-scripts/onion-time-pre-script
__ Status: Subsequent run after boot.
__ Static Time Sanity Check: Within minimum time 'Mon Jun 12 00:00:00 UTC 2023' and expiration timestamp 'Tue May 17 10:00:00 UTC 2033', ok.
__ Tor reports: NOTICE BOOTSTRAP PROGRESS=100 TAG=done SUMMARY="Done"
__ Tor circuit: established
__ Tor Consensus Time Sanity Check: The clock might be too fast. Clock is faster than consensus/valid-until 2023-09-10 14:00:00. extra guess: Tor consensus might be outdated and download might still be in progress since this is the first run after boot.
__ anondate_use: Running 'anondate-set' (by creating file '/run/sdwdate/request_anondate-set')...
__ ### END: ### Exiting with exit_code '2' indicating 'wait, show busy icon and retry.'.
[INFO] [systemcheck] Tor Connection Result:
- Connecting for 14 seconds. | 100 % done. 
- Tor Circuit: established.
- Tor reports: NOTICE BOOTSTRAP PROGRESS=100 TAG=done SUMMARY="Done"
- Timesync status: not done.
- sdwdate reports: Preparation not done yet. More more information,             see: sdwdate-gui -> right click -> Open sdwdate's log
- onion-time-pre-script reports: 
__ ### START: ### /usr/libexec/helper-scripts/onion-time-pre-script
__ Status: Subsequent run after boot.
__ Static Time Sanity Check: Within minimum time 'Mon Jun 12 00:00:00 UTC 2023' and expiration timestamp 'Tue May 17 10:00:00 UTC 2033', ok.
__ Tor reports: NOTICE BOOTSTRAP PROGRESS=100 TAG=done SUMMARY="Done"
__ Tor circuit: established
__ Tor Consensus Time Sanity Check: The clock might be too fast. Clock is faster than consensus/valid-until 2023-09-10 14:00:00. extra guess: Tor consensus might be outdated and download might still be in progress since this is the first run after boot.
__ anondate_use: Running 'anondate-set' (by creating file '/run/sdwdate/request_anondate-set')...
__ ### END: ### Exiting with exit_code '2' indicating 'wait, show busy icon and retry.'.
[INFO] [systemcheck] Tor Connection Result:
- Connecting for 16 seconds. | 100 % done. 
- Tor Circuit: established.
- Tor reports: NOTICE BOOTSTRAP PROGRESS=100 TAG=done SUMMARY="Done"
- Timesync status: not done.
- sdwdate reports: Preparation not done yet. More more information,             see: sdwdate-gui -> right click -> Open sdwdate's log
- onion-time-pre-script reports: 
__ ### START: ### /usr/libexec/helper-scripts/onion-time-pre-script
__ Status: Subsequent run after boot.
__ Static Time Sanity Check: Within minimum time 'Mon Jun 12 00:00:00 UTC 2023' and expiration timestamp 'Tue May 17 10:00:00 UTC 2033', ok.
__ Tor reports: NOTICE BOOTSTRAP PROGRESS=100 TAG=done SUMMARY="Done"
__ Tor circuit: established
__ Tor Consensus Time Sanity Check: The clock might be too fast. Clock is faster than consensus/valid-until 2023-09-10 14:00:00. extra guess: Tor consensus might be outdated and download might still be in progress since this is the first run after boot.
__ anondate_use: Running 'anondate-set' (by creating file '/run/sdwdate/request_anondate-set')...
__ ### END: ### Exiting with exit_code '2' indicating 'wait, show busy icon and retry.'.
[INFO] [systemcheck] Tor Connection Result:
- Connecting for 18 seconds. | 100 % done. 
- Tor Circuit: established.
- Tor reports: NOTICE BOOTSTRAP PROGRESS=100 TAG=done SUMMARY="Done"
- Timesync status: not done.
- sdwdate reports: Preparation not done yet. More more information,             see: sdwdate-gui -> right click -> Open sdwdate's log
- onion-time-pre-script reports: 
__ ### START: ### /usr/libexec/helper-scripts/onion-time-pre-script
__ Status: Subsequent run after boot.
__ Static Time Sanity Check: Within minimum time 'Mon Jun 12 00:00:00 UTC 2023' and expiration timestamp 'Tue May 17 10:00:00 UTC 2033', ok.
__ Tor reports: NOTICE BOOTSTRAP PROGRESS=100 TAG=done SUMMARY="Done"
__ Tor circuit: established
__ Tor Consensus Time Sanity Check: The clock might be too fast. Clock is faster than consensus/valid-until 2023-09-10 14:00:00. extra guess: Tor consensus might be outdated and download might still be in progress since this is the first run after boot.
__ anondate_use: Running 'anondate-set' (by creating file '/run/sdwdate/request_anondate-set')...
__ ### END: ### Exiting with exit_code '2' indicating 'wait, show busy icon and retry.'.
[INFO] [systemcheck] Tor Connection Result:
- Connecting for 20 seconds. | 100 % done. 
- Tor Circuit: established.
- Tor reports: NOTICE BOOTSTRAP PROGRESS=100 TAG=done SUMMARY="Done"
- Timesync status: not done.
- sdwdate reports: Preparation not done yet. More more information,             see: sdwdate-gui -> right click -> Open sdwdate's log
- onion-time-pre-script reports: 
__ ### START: ### /usr/libexec/helper-scripts/onion-time-pre-script
__ Status: Subsequent run after boot.
__ Static Time Sanity Check: Within minimum time 'Mon Jun 12 00:00:00 UTC 2023' and expiration timestamp 'Tue May 17 10:00:00 UTC 2033', ok.
__ Tor reports: NOTICE BOOTSTRAP PROGRESS=100 TAG=done SUMMARY="Done"
__ Tor circuit: established
__ Tor Consensus Time Sanity Check: The clock might be too fast. Clock is faster than consensus/valid-until 2023-09-10 14:00:00. extra guess: Tor consensus might be outdated and download might still be in progress since this is the first run after boot.
__ anondate_use: Running 'anondate-set' (by creating file '/run/sdwdate/request_anondate-set')...
__ ### END: ### Exiting with exit_code '2' indicating 'wait, show busy icon and retry.'.
[INFO] [systemcheck] Tor Connection Result:
- Connecting for 22 seconds. | 100 % done. 
- Tor Circuit: established.
- Tor reports: NOTICE BOOTSTRAP PROGRESS=100 TAG=done SUMMARY="Done"
- Timesync status: not done.
- sdwdate reports: Preparation not done yet. More more information,             see: sdwdate-gui -> right click -> Open sdwdate's log
- onion-time-pre-script reports: 
__ ### START: ### /usr/libexec/helper-scripts/onion-time-pre-script
__ Status: Subsequent run after boot.
__ Static Time Sanity Check: Within minimum time 'Mon Jun 12 00:00:00 UTC 2023' and expiration timestamp 'Tue May 17 10:00:00 UTC 2033', ok.
__ Tor reports: NOTICE BOOTSTRAP PROGRESS=100 TAG=done SUMMARY="Done"
__ Tor circuit: established
__ Tor Consensus Time Sanity Check: The clock might be too fast. Clock is faster than consensus/valid-until 2023-09-10 14:00:00. extra guess: Tor consensus might be outdated and download might still be in progress since this is the first run after boot.
__ anondate_use: Running 'anondate-set' (by creating file '/run/sdwdate/request_anondate-set')...
__ ### END: ### Exiting with exit_code '2' indicating 'wait, show busy icon and retry.'.
[INFO] [systemcheck] Tor Connection Result:
- Connecting for 24 seconds. | 100 % done. 
- Tor Circuit: established.
- Tor reports: NOTICE BOOTSTRAP PROGRESS=100 TAG=done SUMMARY="Done"
- Timesync status: not done.
- sdwdate reports: Preparation not done yet. More more information,             see: sdwdate-gui -> right click -> Open sdwdate's log
- onion-time-pre-script reports: 
__ ### START: ### /usr/libexec/helper-scripts/onion-time-pre-script
__ Status: Subsequent run after boot.
__ Static Time Sanity Check: Within minimum time 'Mon Jun 12 00:00:00 UTC 2023' and expiration timestamp 'Tue May 17 10:00:00 UTC 2033', ok.
__ Tor reports: NOTICE BOOTSTRAP PROGRESS=100 TAG=done SUMMARY="Done"
__ Tor circuit: established
__ Tor Consensus Time Sanity Check: The clock might be too fast. Clock is faster than consensus/valid-until 2023-09-10 14:00:00. extra guess: Tor consensus might be outdated and download might still be in progress since this is the first run after boot.
__ anondate_use: Running 'anondate-set' (by creating file '/run/sdwdate/request_anondate-set')...
__ ### END: ### Exiting with exit_code '2' indicating 'wait, show busy icon and retry.'.
[INFO] [systemcheck] Tor Connection Result:
- Connecting for 26 seconds. | 100 % done. 
- Tor Circuit: established.
- Tor reports: NOTICE BOOTSTRAP PROGRESS=100 TAG=done SUMMARY="Done"
- Timesync status: not done.
- sdwdate reports: Preparation not done yet. More more information,             see: sdwdate-gui -> right click -> Open sdwdate's log
- onion-time-pre-script reports: 
__ ### START: ### /usr/libexec/helper-scripts/onion-time-pre-script
__ Status: Subsequent run after boot.
__ Static Time Sanity Check: Within minimum time 'Mon Jun 12 00:00:00 UTC 2023' and expiration timestamp 'Tue May 17 10:00:00 UTC 2033', ok.
__ Tor reports: NOTICE BOOTSTRAP PROGRESS=100 TAG=done SUMMARY="Done"
__ Tor circuit: established
__ Tor Consensus Time Sanity Check: The clock might be too fast. Clock is faster than consensus/valid-until 2023-09-10 14:00:00. extra guess: Tor consensus might be outdated and download might still be in progress since this is the first run after boot.
__ anondate_use: Running 'anondate-set' (by creating file '/run/sdwdate/request_anondate-set')...
__ ### END: ### Exiting with exit_code '2' indicating 'wait, show busy icon and retry.'.
[INFO] [systemcheck] Tor Connection Result:
- Connecting for 28 seconds. | 100 % done. 
- Tor Circuit: established.
- Tor reports: NOTICE BOOTSTRAP PROGRESS=100 TAG=done SUMMARY="Done"
- Timesync status: not done.
- sdwdate reports: Preparation not done yet. More more information,             see: sdwdate-gui -> right click -> Open sdwdate's log
- onion-time-pre-script reports: 
__ ### START: ### /usr/libexec/helper-scripts/onion-time-pre-script
__ Status: Subsequent run after boot.
__ Static Time Sanity Check: Within minimum time 'Mon Jun 12 00:00:00 UTC 2023' and expiration timestamp 'Tue May 17 10:00:00 UTC 2033', ok.
__ Tor reports: NOTICE BOOTSTRAP PROGRESS=100 TAG=done SUMMARY="Done"
__ Tor circuit: established
__ Tor Consensus Time Sanity Check: The clock might be too fast. Clock is faster than consensus/valid-until 2023-09-10 14:00:00. extra guess: Tor consensus might be outdated and download might still be in progress since this is the first run after boot.
__ anondate_use: Running 'anondate-set' (by creating file '/run/sdwdate/request_anondate-set')...
__ ### END: ### Exiting with exit_code '2' indicating 'wait, show busy icon and retry.'.
[INFO] [systemcheck] Tor Connection Result:
- Connecting for 30 seconds. | 100 % done. 
- Tor Circuit: established.
- Tor reports: NOTICE BOOTSTRAP PROGRESS=100 TAG=done SUMMARY="Done"
- Timesync status: not done.
- sdwdate reports: Preparation not done yet. More more information,             see: sdwdate-gui -> right click -> Open sdwdate's log
- onion-time-pre-script reports: 
__ ### START: ### /usr/libexec/helper-scripts/onion-time-pre-script
__ Status: Subsequent run after boot.
__ Static Time Sanity Check: Within minimum time 'Mon Jun 12 00:00:00 UTC 2023' and expiration timestamp 'Tue May 17 10:00:00 UTC 2033', ok.
__ Tor reports: NOTICE BOOTSTRAP PROGRESS=100 TAG=done SUMMARY="Done"
__ Tor circuit: established
__ Tor Consensus Time Sanity Check: The clock might be too fast. Clock is faster than consensus/valid-until 2023-09-10 14:00:00. extra guess: Tor consensus might be outdated and download might still be in progress since this is the first run after boot.
__ anondate_use: Running 'anondate-set' (by creating file '/run/sdwdate/request_anondate-set')...
__ ### END: ### Exiting with exit_code '2' indicating 'wait, show busy icon and retry.'.
[INFO] [systemcheck] Tor Connection Result:
- Connecting for 32 seconds. | 100 % done. 
- Tor Circuit: established.
- Tor reports: NOTICE BOOTSTRAP PROGRESS=100 TAG=done SUMMARY="Done"
- Timesync status: not done.
- sdwdate reports: Preparation not done yet. More more information,             see: sdwdate-gui -> right click -> Open sdwdate's log
- onion-time-pre-script reports: 
__ ### START: ### /usr/libexec/helper-scripts/onion-time-pre-script
__ Status: Subsequent run after boot.
__ Static Time Sanity Check: Within minimum time 'Mon Jun 12 00:00:00 UTC 2023' and expiration timestamp 'Tue May 17 10:00:00 UTC 2033', ok.
__ Tor reports: NOTICE BOOTSTRAP PROGRESS=100 TAG=done SUMMARY="Done"
__ Tor circuit: established
__ Tor Consensus Time Sanity Check: The clock might be too fast. Clock is faster than consensus/valid-until 2023-09-10 14:00:00. extra guess: Tor consensus might be outdated and download might still be in progress since this is the first run after boot.
__ anondate_use: Running 'anondate-set' (by creating file '/run/sdwdate/request_anondate-set')...
__ ### END: ### Exiting with exit_code '2' indicating 'wait, show busy icon and retry.'.
^Csystemcheck: signal SIGINT received. Cleaning up... Exiting...
[INFO] [systemcheck] systemcheck aborted! (SIGNAL_TYPE: SIGINT)

then this after systemcheck is done 

ERROR: Time Synchronization Result: 
systemcheck gave up waiting. 

Time synchronization status: pending 
sdwdate reports: Preparation not done yet. More more information, see: sdwdate-gui -> right click -> Open sdwdate's log 
whonix_firewall status: first run after boot 
onion-time-pre-script reports: 
__ ### START: ### /usr/libexec/helper-scripts/onion-time-pre-script
__ Status: Subsequent run after boot.
__ Static Time Sanity Check: Within minimum time 'Mon Jun 12 00:00:00 UTC 2023' and expiration timestamp 'Tue May 17 10:00:00 UTC 2033', ok.
__ Tor reports: NOTICE BOOTSTRAP PROGRESS=100 TAG=done SUMMARY="Done"
__ Tor circuit: established
__ Tor Consensus Time Sanity Check: The clock might be too fast. Clock is faster than consensus/valid-until 2023-09-10 14:00:00. extra guess: Tor consensus might be outdated and download might still be in progress since this is the first run after boot.
__ anondate_use: Running 'anondate-set' (by creating file '/run/sdwdate/request_anondate-set')...
__ ### END: ### Exiting with exit_code '2' indicating 'wait, show busy icon and retry.'.

Possible issues:

  • sdwdate will need a few more moments for fetching the time.
  • 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 in Terminal: sudo service sdwdate restart

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.

once this is done it works but then after reboot i have to repeatr this. anyway to fix this?

367

Host clock too fast?

368

Host clock seems to be accurate? Im on macbook air m2 not sure what i can do?

369

The gate way and work station are showing different times too gateway is 1 hr ahed of hostclock time and wrokstation is 2 hr ahead

370

Please read this about UTC:
Post-installation Security Advice chapter Network Time Syncing in Whonix wiki

371

sorry i should of rephrased that, i am aware of what you sent, what i meant was does the wg and ws neet to be the same time? as in in sync or can they vary. Also with the systemcheck clock issue. What can i do fix this? shall i change the country of the host clock or server?

372

There might be an issue that the initial clock setting of the VM because the VM initially gets the time from the host. The issue could be in the VM configuration files.

There’s no utm file for Kicksecure yet:

https://github.com/Kicksecure/libvirt-dist/tree/master/usr/share/kicksecure-utm/Kicksecure.plist

I don’t know how clock can be configured with qemu / utm. Could even be a bug for the virtualizer on that platform.

So this needs development, there’s no contributor working on this, hence unsupported. So most likely won’t be fixable.

Not exactly the same but in most cases at the same hour.

This is weird and that’s why I wrote above in this post.