Hi there,
Qubes 3.1 works fine and connects to the Internet. The TorBrowser-Bundle from Torproject.org also connects without any problems (TOR is not censored in the area where I live.)
Unfortunately the Whonix-VMs do not connect (preinstalled together with Qubes: whonix-ws, -gw, anon-whonix and sys-whonix).
Could you please help me to get Whonix running on Qubes?
(If you need further information, feel free to ask.)
Thank you very much!
Can you please check if it is set up as per
?
Any error messages?
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).
BTW many of these arm messages can be ignored as per https://www.whonix.org/wiki/Tor_Controller#Arm_FAQ.
I don’t have an answer to your actual issue.
Does this persist?
Please also check /var/run/tor/log.
Does the clock within the gateway match the host’s clock within a reasonable amount? Plus or minus 10 minutes or so. Please check by running date inside sys-whonix and dom0.
Also please check your host clock is reasonable correct.
Theoretically, you might have picked a bad Tor entry guard by chance. But that’s unlikely.
You could try if using bridges works better. [Because to suggest using another Tor entry guard would counter the security reason for using Tor entry guards in the first place.]
( Bridges https://www.whonix.org/wiki/Bridges )
Probably the problem is because of different times:
The time in dom0 is equal to the host time, but the clock in sys-whonix (whonix-gw, whonix-ws and anon-whonix) is over 1 hour slow!
sudo timedatectl set-timezone … failed due to access denied.
Here is the output of /var/run/tor/log (sys-whonix):
Dec 29 13:57:59.000 [notice] Tor 0.2.7.6 (git-605ae665009853bd) opening new log file.
Dec 29 13:57:59.472 [notice] Tor v0.2.7.6 (git-605ae665009853bd) running on Linux with Libevent 2.0.21-stable, OpenSSL 1.0.1k and Zlib 1.2.8.
Dec 29 13:57:59.472 [notice] Tor can’t help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Dec 29 13:57:59.472 [notice] Read configuration file “/usr/share/tor/tor-service-defaults-torrc”.
Dec 29 13:57:59.472 [notice] Read configuration file “/etc/tor/torrc”.
Dec 29 13:57:59.475 [notice] You configured a non-loopback address ‘10.137.3.1:9050’ for SocksPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Dec 29 13:57:59.475 [notice] You configured a non-loopback address ‘10.137.3.1:9100’ for SocksPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Dec 29 13:57:59.475 [notice] You configured a non-loopback address ‘10.137.3.1:9101’ for SocksPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Dec 29 13:57:59.475 [notice] You configured a non-loopback address ‘10.137.3.1:9102’ for SocksPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
…
…
…
Dec 29 13:57:59.476 [notice] Opening Socks listener on 10.137.3.1:9155
Dec 29 13:57:59.476 [notice] Opening Socks listener on 10.137.3.1:9156
Dec 29 13:57:59.476 [notice] Opening Socks listener on 10.137.3.1:9157
Dec 29 13:57:59.476 [notice] Opening Socks listener on 10.137.3.1:9158
Dec 29 13:57:59.477 [notice] Opening Socks listener on 10.137.3.1:9159
Dec 29 13:57:59.477 [notice] Opening Socks listener on 10.137.3.1:9160
Dec 29 13:57:59.477 [notice] Opening Socks listener on 10.137.3.1:9161
Dec 29 13:57:59.477 [notice] Opening Socks listener on 10.137.3.1:9162
Dec 29 13:57:59.477 [notice] Opening Socks listener on 10.137.3.1:9163
Dec 29 13:57:59.477 [notice] Opening Socks listener on 10.137.3.1:9164
Dec 29 13:57:59.477 [notice] Opening Socks listener on 10.137.3.1:9165
Dec 29 13:57:59.477 [notice] Opening Socks listener on 10.137.3.1:9166
Dec 29 13:57:59.477 [notice] Opening Socks listener on 10.137.3.1:9167
Dec 29 13:57:59.477 [notice] Opening Socks listener on 10.137.3.1:9168
Dec 29 13:57:59.477 [notice] Opening Socks listener on 10.137.3.1:9169
Dec 29 13:57:59.477 [notice] Opening Socks listener on 10.137.3.1:9170
Dec 29 13:57:59.477 [notice] Opening Socks listener on 10.137.3.1:9171
Dec 29 13:57:59.477 [notice] Opening Socks listener on 10.137.3.1:9172
Dec 29 13:57:59.477 [notice] Opening Socks listener on 10.137.3.1:9173
Dec 29 13:57:59.477 [notice] Opening Socks listener on 10.137.3.1:9174
Dec 29 13:57:59.477 [notice] Opening Socks listener on 10.137.3.1:9175
Dec 29 13:57:59.477 [notice] Opening Socks listener on 10.137.3.1:9176
Dec 29 13:57:59.477 [notice] Opening Socks listener on 10.137.3.1:9177
Dec 29 13:57:59.477 [notice] Opening Socks listener on 10.137.3.1:9178
Dec 29 13:57:59.477 [notice] Opening Socks listener on 10.137.3.1:9179
Dec 29 13:57:59.477 [notice] Opening Socks listener on 10.137.3.1:9180
Dec 29 13:57:59.477 [notice] Opening Socks listener on 10.137.3.1:9181
Dec 29 13:57:59.477 [notice] Opening Socks listener on 10.137.3.1:9182
Dec 29 13:57:59.477 [notice] Opening Socks listener on 10.137.3.1:9183
Dec 29 13:57:59.477 [notice] Opening Socks listener on 10.137.3.1:9184
Dec 29 13:57:59.477 [notice] Opening Socks listener on 10.137.3.1:9185
Dec 29 13:57:59.477 [notice] Opening Socks listener on 10.137.3.1:9186
Dec 29 13:57:59.477 [notice] Opening Socks listener on 10.137.3.1:9187
Dec 29 13:57:59.477 [notice] Opening Socks listener on 10.137.3.1:9188
Dec 29 13:57:59.477 [notice] Opening Socks listener on 10.137.3.1:9189
Dec 29 13:57:59.477 [notice] Opening Socks listener on 127.0.0.1:9050
Dec 29 13:57:59.477 [notice] Opening Socks listener on 127.0.0.1:9100
Dec 29 13:57:59.477 [notice] Opening Socks listener on 127.0.0.1:9101
Dec 29 13:57:59.477 [notice] Opening Socks listener on 127.0.0.1:9102
Dec 29 13:57:59.477 [notice] Opening Socks listener on 127.0.0.1:9103
Dec 29 13:57:59.477 [notice] Opening Socks listener on 127.0.0.1:9104
Dec 29 13:57:59.477 [notice] Opening Socks listener on 127.0.0.1:9105
Dec 29 13:57:59.477 [notice] Opening Socks listener on 127.0.0.1:9106
Dec 29 13:57:59.477 [notice] Opening Socks listener on 127.0.0.1:9107
Dec 29 13:57:59.477 [notice] Opening Socks listener on 127.0.0.1:9108
Dec 29 13:57:59.477 [notice] Opening Socks listener on 127.0.0.1:9109
Dec 29 13:57:59.477 [notice] Opening Socks listener on 127.0.0.1:9110
Dec 29 13:57:59.477 [notice] Opening Socks listener on 127.0.0.1:9111
Dec 29 13:57:59.477 [notice] Opening Socks listener on 127.0.0.1:9112
Dec 29 13:57:59.477 [notice] Opening Socks listener on 127.0.0.1:9113
Dec 29 13:57:59.477 [notice] Opening Socks listener on 127.0.0.1:9114
Dec 29 13:57:59.477 [notice] Opening Socks listener on 127.0.0.1:9115
Dec 29 13:57:59.477 [notice] Opening Socks listener on 127.0.0.1:9116
Dec 29 13:57:59.477 [notice] Opening Socks listener on 127.0.0.1:9117
Dec 29 13:57:59.477 [notice] Opening Socks listener on 127.0.0.1:9118
Dec 29 13:57:59.477 [notice] Opening Socks listener on 127.0.0.1:9119
Dec 29 13:57:59.477 [notice] Opening Socks listener on 127.0.0.1:9120
Dec 29 13:57:59.477 [notice] Opening Socks listener on 127.0.0.1:9121
Dec 29 13:57:59.477 [notice] Opening Socks listener on 127.0.0.1:9122
Dec 29 13:57:59.477 [notice] Opening Socks listener on 127.0.0.1:9123
Dec 29 13:57:59.477 [notice] Opening Socks listener on 127.0.0.1:9124
Dec 29 13:57:59.477 [notice] Opening Socks listener on 127.0.0.1:9125
Dec 29 13:57:59.477 [notice] Opening Socks listener on 127.0.0.1:9150
Dec 29 13:57:59.477 [notice] Opening DNS listener on 10.137.3.1:5300
Dec 29 13:57:59.477 [notice] Opening DNS listener on 127.0.0.1:5400
Dec 29 13:57:59.477 [notice] Opening Transparent pf/netfilter listener on 10.137.3.1:9040
Dec 29 13:57:59.477 [notice] Opening Transparent pf/netfilter listener on 127.0.0.1:9041
Dec 29 13:57:59.477 [notice] Opening Control listener on 127.0.0.1:9051
Dec 29 13:57:59.478 [notice] Opening Control listener on /var/run/tor/control
Dec 29 13:57:59.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip.
Dec 29 13:57:59.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
Dec 29 13:57:59.000 [notice] Bootstrapped 0%: Starting
Dec 29 13:57:59.000 [notice] Signaled readiness to systemd
Dec 29 13:57:59.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:57:59.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:58:00.000 [notice] Bootstrapped 5%: Connecting to directory server
Dec 29 13:58:00.000 [notice] Bootstrapped 10%: Finishing handshake with directory server
Dec 29 13:58:01.000 [notice] Bootstrapped 15%: Establishing an encrypted directory connection
Dec 29 13:58:01.000 [notice] Bootstrapped 20%: Asking for networkstatus consensus
Dec 29 13:58:01.000 [notice] Bootstrapped 25%: Loading networkstatus consensus
Dec 29 13:58:09.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:58:10.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:58:20.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:58:20.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:58:23.000 [warn] Socks version 71 not recognized. (Tor is not an http proxy.)
Dec 29 13:58:23.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:58:23.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:58:26.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:58:26.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:58:28.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:58:28.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:58:30.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:58:30.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:58:30.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:58:31.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:58:33.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:58:33.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:58:35.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:58:35.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:58:37.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:58:37.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:58:40.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:58:40.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:58:40.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:58:40.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:58:42.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:58:42.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:58:44.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:58:44.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:58:47.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:58:47.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:58:49.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:58:49.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:58:50.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:58:50.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:58:51.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:58:51.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:58:54.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:58:54.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:58:56.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:58:56.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:58:58.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:58:58.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:00.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:00.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:01.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:01.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:03.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:03.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:05.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:05.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:08.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:08.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:10.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:10.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:11.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:11.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:12.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:12.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:14.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:15.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:17.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:17.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:19.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:19.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:21.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:21.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:21.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:21.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:24.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:24.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:26.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:26.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:28.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:28.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:31.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:31.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:31.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:31.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:33.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:33.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:35.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:35.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:37.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:37.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:40.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:40.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:41.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:41.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:42.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:42.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:44.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:44.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:46.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:46.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:49.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:49.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:51.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:51.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:51.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:51.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:53.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:53.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:56.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:56.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:58.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 13:59:58.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 14:00:00.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 14:00:00.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 14:00:01.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 14:00:01.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 14:00:02.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 14:00:02.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 14:00:05.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 14:00:05.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 14:00:07.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 14:00:07.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 14:00:09.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 14:00:09.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 14:00:11.000 [notice] New control connection opened from 127.0.0.1.
Dec 29 14:00:11.000 [notice] New control connection opened from 127.0.0.1.
…
…
…
Don’t change timezone inside Whonix. They are deliberately set to UTC.
I.e. host time in UTC should reasonably match time in Whonix VMs in UTC.
…is makes sense. After the post above I’ve read it also here:
I changed all clocks to UTC (BIOS, dom0, whonix-VMs), so that all times are equal.
After a reboot the error (no connection) persists.
How to proceed?
I tried to edit torrc and set bridges – but it doesn’t work, but maybe there’s an error in the edited file?
This is the content of torrc (sys-whonix):
# This file is part of Whonix
# Copyright (C) 2012 - 2013 adrelanos <adrelanos at riseup dot net>
# See the file COPYING for copying conditions.
# Use this file for your user customizations.
# Please see /etc/tor/torrc.examples for help, options, comments etc.
# Anything here will override Whonix's own Tor config customizations in
# /usr/share/tor/tor-service-defaults-torrc
# Enable Tor through whonixsetup or manually uncomment "DisableNetwork 0" by
# removing the # in front of it.
DisableNetwork 0
UseBridges 1
ClientTransportPlugin obfs2,obfs3 exec /usr/bin/obfsproxy managed
ClientTransportPlugin obfs4 exec /usr/bin/obfs4proxy managed
UseBridges 1
ClientTransportPlugin obfs4 exec /usr/bin/obfs4proxy managed
bridge obfs4 69.163.37.128:2483 383FDF8E29F6797F9F386E4D37241EF394B0C112 cert=50ESFeT8xbzSq97BP/4i660u7kPJCCsiXVqvebRZZmAlCN5+NwKngqK6hONw6tRqRXnoQg iat-mode=0
#bridge obfs3 188.166.125.241:58564 53374FCD40E317F6B600FC59490C2D0F431827F1
#bridge obfs3 37.218.246.21:10387 58FDF3A94625DFB0C9DF99B1616757028776E4E6
#bridge obfs3 54.86.81.93:40872 D6C64FBC25D840B0BBFCD766ABC713E66A5FC3D8
#bridge obfs4 37.218.246.25:40083 58FDF3A94625DFB0C9DF99B1616757028776E4E6 cert=uGaqesFv1QfJfeLWDyND4UUd9HPkR64kB7FIUQrhiHXQZMHcOnaMOgvQP9GMJCJyWSyoPg iat-mode=0
#bridge obfs4 104.129.176.152:10950 072B62A5FE3D16598068596E96BE5878FE2A3C65 cert=8I6Qa0kstGhySz2zp5P3vP/mMPv6oMIwdfJMIRaGDqtLdjapibYVEPKYVXJ4i2u6DUQHTA iat-mode=0
#bridge obfs4 69.163.37.128:2483 383FDF8E29F6797F9F386E4D37241EF394B0C112 cert=50ESFeT8xbzSq97BP/4i660u7kPJCCsiXVqvebRZZmAlCN5+NwKngqK6hONw6tRqRXnoQg iat-mode=0No idea.
u8u9:
I changed all clocks to UTC (BIOS, dom0
That wasn’t suggested.
Is this config / bridge known to work outside of Whonix?
You have a duplicate line
ClientTransportPlugin obfs4 exec /usr/bin/obfs4proxy managed
not sure that may cause issues.
All times are (nearly) equal, there are only little differences (about 1 min).
I don’t know if the bridges are working, but the TorBrowser-Bundle is still working fine?!
I changed the torrc again, tried all variants ("#"), but the error persists:
# Please see /etc/tor/torrc.examples for help, options, comments etc.
# Anything here will override Whonix's own Tor config customizations in
# /usr/share/tor/tor-service-defaults-torrc
# Enable Tor through whonixsetup or manually uncomment "DisableNetwork 0" by
# removing the # in front of it.
DisableNetwork 0
UseBridges 1
ClientTransportPlugin obfs2,obfs3 exec /usr/bin/obfsproxy managed
ClientTransportPlugin obfs4 exec /usr/bin/obfs4proxy managed
#UseBridges 1
#ClientTransportPlugin obfs4 exec /usr/bin/obfs4proxy managed
#bridge obfs4 69.163.37.128:2483 383FDF8E29F6797F9F386E4D37241EF394B0C112 cert=50ESFeT8xbzSq97BP/4i660u7kPJCCsiXVqvebRZZmAlCN5+NwKngqK6hONw6tRqRXnoQg iat-mode=0
#bridge obfs3 188.166.125.241:58564 53374FCD40E317F6B600FC59490C2D0F431827F1
#bridge obfs3 37.218.246.21:10387 58FDF3A94625DFB0C9DF99B1616757028776E4E6
#bridge obfs3 54.86.81.93:40872 D6C64FBC25D840B0BBFCD766ABC713E66A5FC3D8
bridge obfs4 37.218.246.25:40083 58FDF3A94625DFB0C9DF99B1616757028776E4E6 cert=uGaqesFv1QfJfeLWDyND4UUd9HPkR64kB7FIUQrhiHXQZMHcOnaMOgvQP9GMJCJyWSyoPg iat-mode=0
bridge obfs4 104.129.176.152:10950 072B62A5FE3D16598068596E96BE5878FE2A3C65 cert=8I6Qa0kstGhySz2zp5P3vP/mMPv6oMIwdfJMIRaGDqtLdjapibYVEPKYVXJ4i2u6DUQHTA iat-mode=0
bridge obfs4 69.163.37.128:2483 383FDF8E29F6797F9F386E4D37241EF394B0C112 cert=50ESFeT8xbzSq97BP/4i660u7kPJCCsiXVqvebRZZmAlCN5+NwKngqK6hONw6tRqRXnoQg iat-mode=0Finally, I’m completely baffled (in a positive way).
Now Qubes/Whonix works! 
sudo qubes-dom0-update --enablerepo=qubes-templates-community qubes-template-whonix-gw qubes-template-whonix-ws
Curiously enough: now the updates of the (unchanged?) TemplateVMs whonix-gw and whonix-ws are working, too.
Let’s hope for the best, that it will continue to work.
However:
BIG thanks to the all Qubes- and Whonix-developers! Kudos! 
Thanks for the report!