Recently whonix is no longer able to sync its time and thus unable to connect to the tor network. When running:
$ whonixcheck --verbose
on the gateway I get the following:
I am unable to link to the screenshots (I have also posted this question on the tor stackexchange):
same question
Rrunning arm on the gateway shows that it is not connected to the tor network:
Looking at the logs suggested by whonixcheck:
tail -f /var/log/sdwdate.log
it can be seen that there is no connection to the network:
The output of timesync on the gateway is:
Checking the logs of timesync
tail -f -n 20 /var/log/sdwdate.log
gives:
timesync 6
I’m also unable to set the hwclock. Running:
date +%T -s “01:01:30”
changes the time locally, but hwclock returns the same time entry as before setting it with date. Also, the time I set is reset on each reboot (both on the gateway and workstation)(I’m running whonix in VirtualBox on a Win7 host machine).
Another thing worth mentioning is that a few days ago I made a dual
boot setup (debian/win7) and booted in debian. I also disabled the UEFI
boot option in BIOS in order to be able to boot from a USB stick and
install debian.
Why isn’t whonix able to sync its time?
Did you try these steps? Troubleshooting - Whonix
Forget about timesync for now. It’s just a follow up issue. First of all, Tor needs to be able to connect.
http://i.stack.imgur.com/ueaZf.png contains questions and advice. Please answer these questions and state how the advice worked for you.
I’ve run into a very weird issue. I have a dual boot setup debian/win7. On the host machines the latest tor browser bundle (I am using the latest stable version (I’ve downloaded it Today)) is unable to connect. It displays a message Loading network status and hangs there. Bellow is the complete output:
http://paste.ubuntu.com/16290983/
Strangely, in one of my virtual machines I’m running an older version of tor that is able to connect. I am behind a NAT on a wireless device. I am also running the browser on a wired machine which is also able to connect. Does tor look at the network interface type? This happens with recent versions of tor.
The logs of type “notice” shown in the GUI are:
5/7/2016 13:01:59 PM.100 [NOTICE] Opening Socks listener on 127.0.0.1:9150
5/7/2016 13:02:00 PM.100 [NOTICE] Bootstrapped 5%: Connecting to directory server
5/7/2016 13:02:00 PM.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server
5/7/2016 13:02:00 PM.300 [NOTICE] Bootstrapped 15%: Establishing an encrypted directory connection
5/7/2016 13:02:00 PM.400 [NOTICE] Bootstrapped 20%: Asking for networkstatus consensus
5/7/2016 13:02:00 PM.400 [NOTICE] Bootstrapped 25%: Loading networkstatus consensus
5/7/2016 13:02:00 PM.500 [NOTICE] I learned some more directory information, but not enough to build a circuit: We have no recent usable consensus.
5/7/2016 13:02:01 PM.100 [WARN] Our clock is 10 hours, 58 minutes behind the time published in the consensus network status document (2016-05-07 21:00:00 UTC). Tor needs an accurate clock to work correctly. Please check your time and date settings!
5/7/2016 13:02:01 PM.100 [NOTICE] I learned some more directory information, but not enough to build a circuit: We have no recent usable consensus.
5/7/2016 13:02:01 PM.300 [NOTICE] I learned some more directory information, but not enough to build a circuit: We have no recent usable consensus.
5/7/2016 13:03:01 PM.600 [NOTICE] I learned some more directory information, but not enough to build a circuit: We have no recent usable consensus.
5/7/2016 13:08:06 PM.400 [NOTICE] I learned some more directory information, but not enough to build a circuit: We have no recent usable consensus.
5/7/2016 13:18:16 PM.500 [NOTICE] I learned some more directory information, but not enough to build a circuit: We have no recent usable consensus.
5/7/2016 13:38:37 PM.100 [WARN] Our clock is 11 hours, 21 minutes behind the time published in the consensus network status document (2016-05-07 22:00:00 UTC). Tor needs an accurate clock to work correctly. Please check your time and date settings!
5/7/2016 13:38:37 PM.100 [NOTICE] I learned some more directory information, but not enough to build a circuit: We have no recent usable consensus.
5/7/2016 13:48:46 PM.400 [NOTICE] I learned some more directory information, but not enough to build a circuit: We have no recent usable consensus.
5/7/2016 13:53:26 PM.800 [NOTICE] Closing no-longer-configured Socks listener on 127.0.0.1:9150
5/7/2016 13:53:26 PM.800 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
5/7/2016 13:53:26 PM.800 [NOTICE] Closing old Socks listener on 127.0.0.1:9150
5/7/2016 13:53:27 PM.100 [NOTICE] Delaying directory fetches: DisableNetwork is set.
There’s too many moving parts. Ambiguous language - can’t understand your situation.
No / Version likely unrelated.
5/7/2016 13:02:01 PM.100 [WARN] Our clock is 10 hours, 58 minutes behind the time published in the consensus network status document (2016-05-07 21:00:00 UTC). Tor needs an accurate clock to work correctly. Please check your time and date settings!
.
May 07 13:02:00.000 [info] connection_dir_client_reached_eof(): Received directory with skewed time (server ‘87.98.162.251:443’): It seems that our clock is behind by 12 hours, 2 minutes, or that theirs is ahead. Tor requires an accurate clock to work: please check your time, timezone, and date settings.
Did you do this? Troubleshooting - Whonix
Then, as Patrick said, get TBB working on your host.
Troubleshooting - Whonix
How can we help? | Tor Project | Support
1 Like
Thanks, the date was offset behind by one day. Now tor can connect both in the host and guest machines.
1 Like
