VNC is possible in theory but I won’t use it due to legal reasons.
Remote Administration - Whonix
And well… Qubes - SSH (soon VNC) into Qubes dom0 - Testers Wanted! requires already functional Whonix.
Very, very few (none in months as far as I can remember) such reports.
Meaning DisableNetwork 1 is still set. In other words, Tor still disabled.
Use anon-connection-wizard (ACW) only once. Or once more. And then leave it. Don’t use it over an over again. There’s really no use. There’s no magic.
All it does is create file /usr/local/etc/torrc.d/40_tor_control_panel.conf and restarts Tor.
More details here:
Unsuitable Connectivity Troubleshooting Tools
If it still doesn’t work, don’t re-use ACW. It won’t help.
If you don’t need bridges (if didn’t need in other VM), then a simpler way to enable Tor with just one line…
sudo setup-dist-noninteractive 1
After that…
cat /usr/local/etc/torrc.d/40_tor_control_panel.conf
Expected output:
# Do not edit this file!
# Please add modifications to the following file instead:
# /usr/local/etc/torrc.d/50_user.conf
DisableNetwork 0
Then re-rerun sudo anon-log. It should no longer “DisableNetwork is set.”. It might show that but not after the latest restart (indicated by “[notice] Interrupt: exiting cleanly.”). Or should not show “DisableNetwork is set.” after reboot (just a shorter, easier to read Tor log).
If you reach this part…
That’s actually “progress”. That’s “only” a connection issue.
But “Tor not running”, Tor disabled or failed Tor control connection are “worse” error conditions.
In that case, perhaps just wait longer. Then restart systemcheck. Tor might finish bootstrapping eventually.
Once there what you can also try:
Tor Consensus Re-Download
Another less safe (but not less safe then re-installing Tor Browser Bundle), see documented risks, last resort:
Unsafe Guard Rotation Methods