Jump to: navigation, search



This page needs a revision. Should distinguish between troubleshooting network issues vs other issues.

Installation and Network Issues[edit]


This introduction is a summary of the basic troubleshooting instructions. It will be described below in greater details. This basically boils down to:

  1. If you haven't already done, verify the Whonix virtual machine images.
  2. Make sure you have imported the Virtual Machines into a supported virtualizer.
  3. Check if Tor Browser works for you on the host.
  4. Check if other virtual machines, ones you created yourself or from a different vendor have working internet.

Include all these information in a support request or bug report.

Before you start[edit]

Verify the Whonix virtual machine images.

On the host[edit]


Always test first, if your host internet connection is working. (ping, ping google.com, etc). On your host:

ping google.com

Check time.


sudo dpkg-reconfigure -a must not show any errors. Will take a while...

sudo dpkg-reconfigure -a

sudo dpkg --configure -a must be silent, i.e. not show any errors, must show output at all. Will take a while...

sudo dpkg --configure -a

Get all updates:

sudo apt-get update
sudo apt-get dist-upgrade

Get the Tor Browser Bundle from torproject.org and test if it is working.

## If you can not get the Tor Browser Bundle to work,
## you will most certainly not get Whonix to work either.
## In the Whonix Documentation it is recommended to have a current
## copy of the Tor Browser Bundle at all times.
## The Tor Browser Bundle is great for testing if you live in a
## censored area or not, if Tor is blocked by your ISP or not.
## When you need (private) (obfuscated) bridges for the Tor Browser Bundle,
## you will need them for Whonix as well.

No network inside Whonix?[edit]

  1. Please install some operating system in one of your own virtual machine or download a regular image without Tor enforcement elsewhere.
  2. Try if networking is functional in the freshly downloaded non-Whonix virtual machine.
  3. If it is not working: then Whonix won't work either. You need to sort that out first. Try re-installing your virtualizer. Reboot. Try again.
  4. If it is working: add this to your support request or bug report, that networking in other non-Whonix VMs is working.

On the Gateway[edit]

As user user[edit]

Login as user user.

sudo su user

Check your route command, make sure the network is associated with eth1.


Check if Tor is running with 'pgrep tor -l', this should return something like "103 tor". If not try 'sudo service tor start' and check for any errors.

pgrep tor -l

Check the status of Tor.

sudo service tor status

Should reply with.

tor is running.

Restart Tor.

sudo service tor restart

Tor should show only notices, no errors.

Verify Tor configuration is valid:

sudo -u debian-tor tor --verify-config

You should see confirmation:

Configuration was valid

Ping the Whonix-Workstation.


Should show Packet filtered.

nslookup should NOT work.

nslookup google.com

Should show timeout.

As user clearnet[edit]

The following test might reveal, that you are a Whonix user. Omit them, if that is of concern for you.

Try if a non-torified, non-anonyomus, direct connection to check.torproject.org is possible. [1]

sudo -u clearnet UWT_DEV_PASSTHROUGH=1 curl --tlsv1.2 --proto =https -H 'Host: check.torproject.org' -k

Tests on both Virtual Machines[edit]

Run the following tests on Whonix-Gateway and on Whonix-Workstation.

Login as user user.

sudo su user

Check time.


sudo dpkg-reconfigure -a must not show any errors. Will take a while...

sudo dpkg-reconfigure -a

sudo dpkg --configure -a must be silent, i.e. not show any errors, must show output at all. Will take a while...

sudo dpkg --configure -a

Test update-grub.

sudo update-grub

Run 'locale'. Must not report any error.

sudo locale

Restart networking:

sudo service networking restart

Apt-get must be fully functional.

sudo apt-get update
sudo apt-get dist-upgrade

Test whonixcheck.


Test whonixcheck with debugging.

whonixcheck --verbose

Check the timezone.

cat /etc/timezone

Must be Etc/UTC.

Clock Fix[edit]

On the host.

Make sure your host clock is set to the correct time.

Find out the time in UTC. For example, run the following command on the host. (In Qubes terms: in dom0)

date -u

Should how something like the following.

Mon Mar 14 17:48:38 UTC 2016

In Whonix-Gateway.

Set the correct time in Whonix-Gateway. (You still need to adjust it.)

sudo date --set "Mon Mar 14 17:48:38 UTC 2016"

Tor should work now. You can test that using whonixcheck.

Restart sdwdate.

sudo service sdwdate restart

If Tor does not work yet, try restarting Tor.

sudo service tor restart
  1. Only uses TCP, no DNS.

Qubes specific[edit]

Connectivity Issue[edit]

Shut down sys-whonix. Set sys-whonix NetVM setting from sys-firewall to sys-net. Restart sys-whonix. Perhaps that helps. This should not be considered a final solution. Contribute to the Qubes bug report: https://github.com/QubesOS/qubes-issues/issues/2141


Random News:

Love Whonix and want to help spread the word? You can start by telling your friends or posting news about Whonix on your website, blog or social media.

https | (forcing) onion

Share: Twitter | Facebook

This is a wiki. Want to improve this page? Help is welcome and volunteer contributions are happily considered! See Conditions for Contributions to Whonix, then Edit! IP addresses are scrubbed, but editing over Tor is recommended. Edits are held for moderation.

Whonix is a licensee of the Open Invention Network. Unless otherwise noted, the content of this page is copyrighted and licensed under the same Libre Software license as Whonix itself. (Why?)