How-to: Fix dom0 Qubes-Whonix ™ UpdatesProxy Settings

If you see the following warning...

WARNING: Execution of /usr/bin/apt-get prevented by /etc/uwt.d/40_qubes.conf because no torified Qubes updates proxy found.

If this warning message is transient, it can be safely ignored. Otherwise, try one of the fixes below.

Update dom0

To launch a dom0 terminal, click the Qubes App Launcher (blue/grey "Q") and then open the Terminal Emulator (Xfce Terminal).

Upgrade Qubes dom0. This step is mandatory.

sudo qubes-dom0-update

sudo qubes-dom0-update

TemplateVMs

Error Resolution Methods

The following fixes are listed in order of preference.

Salt Fix

Use salt to setup dom0 settings.

sudo qubesctl state.sls qvm.anon-whonix

sudo qubesctl state.sls qvm.anon-whonix

Next, check if the problem has been corrected. Run the following command in Whonix ™ TemplateVM.

sudo systemctl restart qubes-whonix-torified-updates-proxy-check

sudo systemctl restart qubes-whonix-torified-updates-proxy-check

Then try to update / use apt-get again.

If there are still problems, try the manual fix below.

Manual Fix

Please make sure Whonix-Gateway ™ (sys-whonix) is running.

• Qubes R3.2: The NetVM of this TemplateVM should be set to Whonix-Gateway ™ (sys-whonix).
• Qubes R4 or higher: Check the dom0 /etc/qubes-rpc/policy/qubes.UpdatesProxy settings.

At the very top of that file, the following text should appear.

$tag:whonix-updatevm $default allow,target=sys-whonix

$tag:whonix-updatevm $default allow,target=sys-whonix

If it is not there, add it.

To view a complete example of the /etc/qubes-rpc/policy/qubes.UpdatesProxy file, please press on expand on the right.

/etc/qubes-rpc/policy/qubes.UpdatesProxy ^[archive] (raw ^[archive]):

## Note that policy parsing stops at the first match,
## so adding anything below "$anyvm $anyvm action" line will have no effect

## Please use a single # to start your custom comments

# Upgrade all TemplateVMs through sys-whonix.
#$type:TemplateVM $default allow,target=sys-whonix

# Upgrade Whonix TemplateVMs through sys-whonix.
$tag:whonix-updatevm $default allow,target=sys-whonix

# Deny Whonix TemplateVMs using UpdatesProxy of any other VM.
$tag:whonix-updatevm $anyvm deny

# Default rule for all TemplateVMs - direct the connection to sys-net
$type:TemplateVM $default allow,target=sys-net

$anyvm $anyvm deny

If Multiple Qubes-Whonix ™ TemplateVMs are configured -- like when the Whonix ™ TemplateVM is cloned -- please press on expand on the right.

The following syntax should apply.

Name-Of-Whonix-TemplateVM $default allow,target=Whonix-Gateway-TemplateBased-ProxyVM

Name-Of-Whonix-TemplateVM $default allow,target=Whonix-Gateway-TemplateBased-ProxyVM

Example entry for Whonix-Gateway ™ TemplateVM.

whonix-gw-15 $default allow,target=sys-whonix

whonix-gw-15 $default allow,target=sys-whonix

Example entry for Whonix-Workstation ™ TemplateVM.

whonix-ws-15 $default allow,target=sys-whonix

whonix-ws-15 $default allow,target=sys-whonix

To test if it is fixed, run the following command in Whonix ™ TemplateVM.

sudo systemctl restart qubes-whonix-torified-updates-proxy-check

sudo systemctl restart qubes-whonix-torified-updates-proxy-check

Then try to update / use apt-get again.

Reinstallation Fix

If the salt and manual fix attempts both fail, then follow the steps to Reinstall Qubes-Whonix ™ TemplateVMs. If reinstallation also fails, then ask for support in the Whonix ™ forums ^[archive].

dom0

Qubes dom0 does not use Qubes UpdatesProxy. Therefore file /etc/qubes-rpc/policy/qubes.UpdatesProxy does not influence which VM will be used by dom0 for fetching updates.

For completeness sake, see below on how to configure Qubes dom0 UpdateVM setting.

To force dom0 updates over Tor, set Qubes' dom0 UpdateVM to sys-whonix.

Qube Manager → System → Global Settings → Dom0 UpdateVM: sys-whonix → OK

To revert this change, set Qubes' dom0 UpdateVM to sys-firewall or another preferred VM.

Qubes Manager → System → Global Settings → Dom0 UpdateVM: sys-firewall → OK

Development

The following development resources are recommended for interested readers:

• https://github.com/Whonix/qubes-whonix/blob/master/etc/uwt.d/40_qubes.conf ^[archive]
• https://github.com/Whonix/qubes-whonix/blob/master/usr/share/uwt/qubes_torfied_dom0.txt ^[archive]
• https://github.com/Whonix/qubes-whonix/blob/master/lib/systemd/system/qubes-whonix-torified-updates-proxy-check.service ^[archive]
• https://github.com/Whonix/qubes-whonix/blob/master/usr/lib/qubes-whonix/init/torified-updates-proxy-check ^[archive]
• https://github.com/QubesOS/qubes-core-admin/blob/master/qubes-rpc-policy/qubes.UpdatesProxy.policy ^[archive]
• https://github.com/Whonix/uwt ^[archive]

Footnotes

---

Whonix ™ is Supported by Evolution Host DDoS Protected VPS. Stay private and get your VPS with Bitcoin or Monero.

---

Follow:

Donate:

Share: Twitter | Facebook

We are looking for video makers to help create demonstration, promotional and conceptual videos or tutorials.

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 ^[archive] of the Open Invention Network ^[archive]. 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 ^[archive]. Debian is a registered trademark ^[archive] owned by Software in the Public Interest, Inc ^[archive].

Whonix ™ is produced independently from the Tor® ^[archive] anonymity software and carries no guarantee from The Tor Project ^[archive] 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.