Whonix-updatevm bug

What’s the output of these commands in dom0?

qvm-service sys-whonix | grep upd
qvm-features sys-whonix | grep upd

What’s the output of this command in sys-whonix?

sudo systemctl status qubes-updates-proxy-forwarder.socket | cat

[user@dom0 ~]$ qvm-service sys-whonix | grep upd
updates-proxy-setup on
[user@dom0 ~]$ qvm-features sys-whonix | grep upd
service.updates-proxy-setup 1

user@host:~$ sudo systemctl status qubes-updates-proxy-forwarder.socket | cat
● qubes-updates-proxy-forwarder.socket - Forward connection to updates proxy over Qubes RPC
Loaded: loaded (/lib/systemd/system/qubes-updates-proxy-forwarder.socket; enabled; preset: enabled)
Active: active (listening) since Sat 2024-10-05 12:41:24 UTC; 3h 34min ago
Listen: 127.0.0.1:8082 (Stream)
Accepted: 16; Connected: 0;
Tasks: 0 (limit: 500)
Memory: 4.0K
CPU: 6ms
CGroup: /system.slice/qubes-updates-proxy-forwarder.socket
Oct 05 12:41:24 host systemd[1]: Listening on qubes-updates-proxy-forwarder.socket - Forward connection to updates proxy over Qubes RPC.

Did you enable updates-proxy-setup for sys-whonix? You shouldn’t enable the use of another update proxy (cacher) in an update proxy qube (sys-whonix):

  • updates-proxy-setup (and its deprecated name: yum-proxy-setup) - use a proxy provided by another VM (instead of downloading updates directly), enabled by default in all templates

How to install software | Qubes OS

To use sys-whonix as an update proxy you need to enable qubes-updates-proxy service for it.

Well, the thing I didn’t try was to set stock gw for sys-whonix template, and once I did, it worked.

I’m baffled totally. The template I’m firing the least is gw. Simply no need for it, once I set sys-whonix,several years ago, and just changing its template to a new gw release(-upgrade)…

Thanks for your time.

SInce I started to use Qubes, I never set this service manually for any qube (if you meant on manual set), and I never had a problem?

I don’t see it in any netVM Services tab too.

I don’t know how could it be enabled without the action of the user.
Maybe you run some script/salt in dom0 that modified it without your knowledge?