I followed all the steps for installation of bridges via qubes whonix shown on the whonix website here:
But when I get to the final step, namely:
Check Tor’s daemon status.
sudo service tor@default status
It should include a a message saying.
Active: active (running) since …
I get the following:
user@host:~$ sudo service tor@default status
● tor@default.service - Anonymizing overlay network for TCP
Loaded: loaded (/lib/systemd/system/tor@default.service; static)
Drop-In: /lib/systemd/system/tor@default.service.d
└─30_qubes.conf, 40_qubes.conf
Active: inactive (dead)
start condition failed at Wed 2017-09-27 02:47:31 UTC; 3min 37s ago
ConditionPathExists=/var/run/qubes-service/whonix-gateway was not met
Sep 27 02:47:31 host systemd[1]: Started Anonymizing overlay network for TCP.
Does this mean I didnt properly configure the bridge? If so, why am I not getting what the whonix site is saying I should get? Anything would help alot. Thanks in advance!
I guess my confusion is that there are so many different VM’s - some labeled ServiceVM, some labeled TemplateVM Some labeled Domain, and then there are variations and colors of each.
I guess it would really help if you let me know which precise VM I apply the changes to in terminal, and which precise one I actually use to access the tor browser. Also, which one do I use to apply the bridges settings to? Having a hard time finding tutorials on this basic issue online. Anything would help. Thanks!
If you used the Bridge instructions in whonix-ws ( Template or appVM ) it would be a good idea to start fresh.
If you are confused on the terminology used in the instructions ( i.e. What is meant by Whonix-gateway, Whonix-workstation Templates; sys-whonix, anon-whonix VMs ) you could read over the Qubes/Install page. It may help clarify things a little for you.
If you used the Bridge instructions in whonix-ws ( Template or appVM ) it would be a good idea to start fresh.
Doing it in a template requires sys-whonix behing deleted and recreated.
We don’t really recommend that but that may work. bind-dirs probably
makes this a confusing process.