Last update: March 17, 2019. This website uses cookies. By using our website, you acknowledge that you have read, understood and agreed to our Privacy Policy, Cookie Policy, Terms of Service, and E-Sign Consent. More information

 Actions

Troubleshooting

Introduction[edit]

The following steps summarize basic troubleshooting instructions, which are described in greater detail below. In basic terms:

  1. Non-Qubes-Whonix ™ only: Verify the Whonix ™ virtual machine images if this has step has not previously been completed.
  2. Ensure the virtual machine images have been imported into a supported virtualizer.
  3. Check if Tor Browser works on the host.
  4. Check if other virtual machines have Internet connectivity, such as newly created ones or those from a different vendor.

Information pertaining to these points should be included in any support request or bug report.

Troubleshooting Steps[edit]

General[edit]

It is recommended to first test if the host Internet connection is functional by using ping. [1] On the host, run.

ping google.com

Check the date and time.

date

The following command should not show any errors. [2]

sudo dpkg-reconfigure -a

The following command should be silent and not show any errors or output at all. [2]

sudo dpkg --configure -a

Next attempt to retrieve all available updates.

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

Download the Tor Browser Bundle from torproject.org and test if it is working on the host; follow one of the methods outlined in Non-Whonix ™ Tor Browser.

If the Tor Browser Bundle is not functional on the host, then Whonix ™ is unlikely to work either. It is recommended to have a recent Tor Browser Bundle version installed at all times. This way users can test if they live in a censored area or not and whether Tor is blocked by the ISP. Further, if (private) (obfuscated) bridges are necessary for Tor Browser Bundle functionality on the host, then Whonix ™ will similarly require them.

Whonix ™ Network Connectivity Problems[edit]

If networking is unavailable inside Whonix ™, then try:

  1. Installing an operating system in a non-Whonix ™ virtual machine or downloading a regular image without Tor enforcement.
  2. Testing network functionality in a freshly downloaded non-Whonix ™ virtual machine.

If networking is still not functional, then Whonix ™ will not work either. The user must first resolve this issue, which might require re-installation of the virtualizer, followed by a reboot and further connectivity test(s).

If networking is functional, then users should note that networking is working in non-Whonix ™ VMs as part of the support request or bug report.

whonixcheck[edit]

Run whonixcheck to verify that the Whonix ™ system is up-to-date and that everything is in proper working order.

Clock Fix[edit]

The first step should be completed on the host to ensure the host clock is set to the correct time.

On the host (Qubes-Whonix ™: dom0), run the following command to report the time in UTC.

date -u

The output should be similar to the following.

Mon Apr 22 04:30:44 UTC 2019

To set the correct time in Whonix-Gateway ™ (sys-whonix), run the following command with the correct date and time parameters.

sudo date --set "Mon Apr 22 04:30:44 UTC 2019"

Tor should work once correct clock values are set, but that can be manually tested with whonixcheck.

Next restart sdwdate.

sudo service sdwdate restart

If Tor is still not functional, try restarting Tor.

sudo service tor restart

Clearnet Connectivity Test[edit]


Users can check if a non-torified, non-anonyomus, direct connection to check.torproject.org is functional. [3]

On Whonix-Gateway ™, run.

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

Qubes-specific[edit]

Connectivity Issue[edit]

Complete the following steps:

  1. Shut down sys-whonix.
  2. Change the sys-whonix NetVM setting from sys-firewall to sys-net.
  3. Restart sys-whonix.

This procedure might help, but should not be considered a final solution. [4]

Low RAM Issues[edit]

When available RAM is insufficient to meet the Whonix ™ VM requirements, problems can emerge which make the VM(s) unusable. Factors that commonly contribute to low RAM issues in Whonix ™ include:

  • Unnecessary processes running and/or multi-tasking on the host OS.
  • Multiple browser tabs being open.
  • Unnecessary processes running in the Whonix ™ VM(s).
  • Allocating more RAM to the Whonix ™ VM than is available; this prevents the VM from booting.
  • Insufficient RAM allocated to the Whonix ™ VM(s).
  • Other non-Whonix ™ VMs running in parallel.

While insufficient RAM can cause a host of issues, behaviors most commonly seen with low memory resources include:

  • Applications are slow or unresponsive.
  • The virtual machine, mouse and/or keyboard freeze.
  • Scrolling causes window staggers or jumps.
  • Issues become worse when additional browser tabs or processes are spawned.
  • Overall performance is poor.

Free up Additional Memory Resources[edit]

If additional memory is needed for the virtual machine, then free up resources and/or add more RAM to the virtual machine:

  • Terminate any non-essential processes on the host.
  • Shutdown any non-essential VMs.
  • Shutdown and/or close non-essential processes and browser tabs in Whonix ™ VMs.
  • Non-Qubes-Whonix ™ only: If low memory issues are experienced in Whonix-Workstation ™, additional resources can be freed by reducing RAM in Whonix-Gateway ™ with rads.

To add additional RAM to the Whonix ™ VM(s), follow the platform-specific advice below.

KVM[edit]

  1. Shutdown the virtual machine(s).
    virsh -c qemu:///system shutdown <vm_name>
  2. Increase maximum memory.
    virsh setmaxmem <vm_name> <memsize> --config
  3. Set actual memory.
    virsh setmem <vm_name> <memsize> --config
  4. Restart the virtual machine(s).
    virsh -c qemu:///system start <vm_name>

Qubes-Whonix ™[edit]

Utilize Qube Manager:

  • Qube Manager -> VM_name -> Qubes settings -> Advanced -> Max memory: mem_size

VirtualBox[edit]

  1. To add RAM in VirtualBox the VM must first be powered down.
  2. Virtual machine -> Menu -> Settings -> Adjust Memory slider -> Hit: OK

Footnotes[edit]

  1. For example, ping 8.8.8.8, ping google.com and so on.
  2. 2.0 2.1 This process can be lengthy.
  3. This test only uses TCP and not DNS.
  4. This procedure was useful for Qubes-Whonix ™ R3.2 users, although the Qubes bug report is now resolved: https://github.com/QubesOS/qubes-issues/issues/2141

No user support in comments. See Support.

Comments will be deleted after some time. Specifically after comments have been addressed in form of wiki enhancements. See Wiki Comments Policy.


Add your comment
Whonix welcomes all comments. If you do not want to be anonymous, register or log in. It is free.


Random News:

We are looking for maintainers and developers.


https | (forcing) onion

Share: Twitter | Facebook

This is a wiki. Want to improve this page? Help is welcome and volunteer contributions are happily considered! Read, understand and agree to Conditions for Contributions to Whonix ™, then Edit! Edits are held for moderation.

Copyright (C) 2012 - 2019 ENCRYPTED SUPPORT LP. Whonix ™ is a trademark. Whonix ™ is a licensee of the Open Invention Network. Unless otherwise noted, the content of this page is copyrighted and licensed under the same Freedom Software license as Whonix ™ itself. (Why?)

Whonix ™ is a derivative of and not affiliated with Debian. Debian is a registered trademark owned by Software in the Public Interest, Inc.

Whonix ™ is produced independently from the Tor® anonymity software and carries no guarantee from The Tor Project about quality, suitability or anything else.

By using our website, you acknowledge that you have read, understood and agreed to our Privacy Policy, Cookie Policy, Terms of Service, and E-Sign Consent. Whonix ™ is provided by ENCRYPTED SUPPORT LP. See Imprint.