I am a long-time user of Whonix and Qubes 3.2. The following issues are specific to the Whonix Workstation on Qubes 3.2.
Firstly, I should start by saying that I ran into the updating problems with the onion repositories. I fixed those by commenting out the onion addresses in the Whonix Workstation TemplateVM (I didn’t have to do this with the Gateway TemplateVM, which didn’t cause me any problems for some reason).
Unfortunately, I am still unable to access the internet from any of my Whonix-ws-14-based AppVMs, and this has been a problem I have been having since the last update. Here’s what happens:
When I first open the Tor Browser, I receive a warning that my activities may be linked if the Tor Browser is already running. I have gotten this sort of warning in the past when I already have an instance of the TB running, but that’s not the case here.
I click “yes” to get rid of the warning box and the Tor Browser proceeds to open. The first sign that something is (still) not right is that it’s unable to find the local Whonix splash page file that always pops up when the browser first starts. Weird, but certainly not a huge issue.
Then, when I try to do a random search (I use DDG’s Onion service to conduct searches), I’m told that the server has reloaded while the request was being made (or something to that effect; it’s a super-common error message). Whatever the cause may be, the result is that I’m unable to visit any website; Google, DDG Onion, DDG Clearnet, and so on all give me the same error.
It occurred to me that this might be a Tor Browser problem, so I opened up the Electrum bitcoin client in the same AppVM to see if that works. Unfortunately, Electrum doesn’t connect either.
Then—again in the same AppVM—I open up konsole and ping google (both google.com and 220.127.116.11): Interestingly, when I ping google.com the terminal shows me the site’s corresponding numerical IPv4 address, so there must be some sort of DNS access at the very least, right? Anyway, aside from seeing the IPv4 address I get no feedback whatsoever for the next 20-30 seconds, so I finally Ctrl-C the process and see a packet loss of 100%.
Finally, I open Firefox in my “Untrusted” AppVM, which uses Fedora 28 as its template and sys-whonix as its NetVM. It takes me to Google without the slightest problem.
Any ideas? Is this just a bad update I’m going to have to wait out, or are there steps I can take to remedy the situation in the meantime? 90% of my Qubes work is done on Whonix, so this has been a major hit to my productivity.
Any help would be greatly appreciated!