I have a clean install of Qubes R3.0 and I have installed and updated the whonix-gw and whonix-ws templates and created their respective virtual machines, all as described in How-to: Install the Stable Version of Qubes-Whonix ™ 16 . I have not messed with any other settings and am not using AppArmor.
When I start my whonix-gw based proxyVM it seems to take a VERY long time to connect to Tor. I have left arm open and documented the messages in the following screenshots
Once it finally manages to complete bootstrap timesync does it’s thing and whonixcheck is happy and everything seems to work fine from then on.
The whonix gateway is using the qubes default sys-firewall as it’s netVM same as all the other appVMs on the system and these all have consistant internet access. Running the Tor browser bundle independently of whonix connects fine and takes ~12sec to establish a circuit which is why I am confused. I have not changed any settings and I am not using any bridges.
I have run multiple searches for information, looked through the wiki and the forums but I have not found anything that mirrors this particular problem. Maybe I am missing something obvious? I would appreciate any pointers on how to diagnose this issue.
:EDIT: Apologies for the big ass images I should have just posted the log. Must be temporary brain damage :-/
My area is not censored as far as I know (although I don’t trust my ISP). I am writing this from Tor browser bundle in an appVM which connects without bridges in a matter of seconds. This is why I am confused by the behaviour of whonix Tor as they are both using the name clearnet proxyVM.
This problem has been going on for days and appears to be getting worse. The other day I was able to stay connected in irc long enough to have an argument with someone :-s but now it drops out before whonixcheck can finish. This last attempt took tor 1.5 hours to bootstrap 100% and whonixcheck passed but timesync failed (log shows requests timing out). Checking the second page in arm has shown 6 different guard nodes in the last 15 minutes and now it appears to have dropped all circuits. Would it be cycling through different entry guards due to communication issues?
sorry, if this may seem like a very rudimentary tip, but did you try installing the Gateway and Workstation a second time? Maybe something simply went wrong there, because your times seem really far longer than any scenario would justify. Furthermore, have you verified the images? Maybe they are simply faulty. Furthermore, does restarting and or reloading TOR in the Gateway show any kind of change on the logs?