Whonix has been setup automatically after the Qubes installation / during the user creation.
The settings of the Whonix-VMs in the Qubes VM Manager look like the screenshots here: https://www.whonix.org/wiki/Qubes/Install
The output of the whonixcheck (anon-whonix AppVM):
INFO: SocksPort Test Result: Connected to Tor. IP: 109.163.234.9
ERROR: TransPort Test Result: Tor’s TransPort was not reachable.
It is normal for this error to temporarily occur.
(If you disabled Tor’s TransPort, please disable this check, see whonixcheck /etc/whonix.d/30_whonixcheck_default configuration file.)
(curl exit code: [6] - [Couldn’t resolve host. The given remote host was not resolved.])
ERROR: Stream Isolation Test: Skipped, because TransPort test failed! Can not test stream isolation.
INFO: Whonix News Result:
√ Up to date: whonix-workstation-packages-dependencies 2.9-1
√ Up to date: Whonix Build Version: 12.0.0.3.2
whonixcheck (sys-whonix) says:
This is the result of the whonixcheck (sys-whonix):
ERROR: SocksPort Test Result: *****://check.torproject.org was not reachable.
You could check, if you can reach *****://check.torproject.org via the Tor Browser Bundle.
(curl exit code: [7] - [Failed to connect to host.])
INFO: Whonix News Result:
√ Up to date: whonix-gateway-packages-dependencies 2.9-1
√ Up to date: Whonix Build Version: 12.0.0.3.2
The Arm - Tor Controller (also sys-whonix) says:
23:02:19 [NOTICE] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving
up. (waiting for circuit) [156 duplicates hidden]
23:00:50 [NOTICE] No circuits are opened. Relaxed timeout for circuit 445 (a Measuring circuit timeout 3-hop circuit in state doing handshakes with channel state open) to 62582ms. However, it appears the circuit has timed out anyway. 7 guards are live.
22:54:08 [NOTICE] Tor now sees network activity. Restoring circuit build timeout recording. Network was down for 98 seconds during 4 circuit attempts.
22:53:35 [NOTICE] Tor has not observed any network activity for the past 65 seconds.
Disabling circuit build timeout recording.
22:52:31 [NOTICE] Tor now sees network activity. Restoring circuit build timeout
recording. Network was down for 73 seconds during 1 circuit attempts.
22:52:29 [NOTICE] Tor has not observed any network activity for the past 72 seconds. Disabling circuit build timeout recording.
22:48:59 [WARN] Your Guard donaTor ($D3044D67B9847CF7ACA446C96D126BA2CE2CDB2F) is
failing to carry an extremely large amount of streams on its circuits. This could indicate a route manipulation attack, network overload, bad local network connecti-vity, or a bug. Use counts are 16/27. Success counts are 21/34. 34 circuits comple-ted, 11 were unusable, 2 collapsed, and 123 timed out. For reference, your timeout cutoff is 63 seconds.
22:48:38 [NOTICE] New control connection opened. [25 duplicates hidden]
22:47:54 [NOTICE] Tor now sees network activity. Restoring circuit build timeout recording. Network was down for 74 seconds during 1 circuit attempts. [1 duplicate hidden]
22:47:53 [NOTICE] Tor has not observed any network activity for the past 73 seconds.
Disabling circuit build timeout recording. [2 duplicates hidden]
22:45:23 [NOTICE] Tor now sees network activity. Restoring circuit build timeout recording. Network was down for 74 seconds during 3 circuit attempts. [1 duplicate hidden]
22:44:19 [NOTICE] Tried for 124 seconds to get a connection to [scrubbed]:0. Giving up. [4 duplicates hidden]
22:42:55 [NOTICE] Tor now sees network activity. Restoring circuit build timeout recording. Network was down for 64 seconds during 1 circuit attempts.
22:42:55 [NOTICE] Tor has not observed any network activity for the past 64 seconds.
Disabling circuit build timeout recording. [1 duplicate hidden]
22:42:46 [NOTICE] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit) [3 duplicates hidden]
22:39:27 [NOTICE] Tor now sees network activity. Restoring circuit build timeout recording. Network was down for 74 seconds during 2 circuit attempts.
22:39:20 [NOTICE] Tor has not observed any network activity for the past 67 seconds. Disabling circuit build timeout recording.
22:36:45 [NOTICE] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for rendezvous desc)
22:35:17 [NOTICE] Tried for 129 seconds to get a connection to [scrubbed]:0. Giving up. [4 duplicates hidden]
22:30:33 [NOTICE] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
22:29:47 [NOTICE] Tor now sees network activity. Restoring circuit build timeout recording. Network was down for 109 seconds during 1 circuit attempts.
22:29:46 [NOTICE] Tor has not observed any network activity for the past 108 seconds.
Disabling circuit build timeout recording.
22:28:41 [WARN] Socks version 71 not recognized. (Tor is not an http proxy.) [1 dupl-icate hidden]
22:28:31 [NOTICE] New control connection opened from 127.0.0.1. [1 duplicate hidden]
22:26:23 [ARM_NOTICE] Unable to prepopulate bandwidth information (insufficient uptime)
22:26:23 [ARM_WARN] The torrc differs from what tor’s using. You can issue a sighup to reload the torrc values by pressing x.
- configuration values are missing from the torrc: HiddenServiceStatistics, RunAsD-aemon
22:26:23 [ARM_NOTICE] Tor is preventing system utilities like netstat and lsof from working. This means that arm can’t provide you with connection information. You can change this by adding ‘DisableDebuggerAttachment 0’ to your torrc and restarting
tor. For more information see…
****://trac.torproject.org/3313
22:26:23 [ARM_NOTICE] No armrc loaded, using defaults. You can customize arm by
placing a configuration file at ‘/home/user/.arm/armrc’ (see the armrc.sample for its options).