I got updatecheck failed on Whonix-Gateway user session after I changed a password for a sysmaint user in sysmaint session. Do I need to clear sysmaint password and leave it without any?
Assistance is needed.
Updatecheck sometimes just fails due to the inherent flakiness of the Tor network. Sometimes a connection can be established right away and just works, sometimes it can stall for a long time and updatecheck ends up timing out. The failure is almost certainly unrelated to changing the sysmaint password, since there’s nothing updatecheck does that depends on the sysmaint password.
1 Like
Documentation and debugging:
Update Notifications by updatecheck
Logs (leaprun read-systemctl-logs-failed-units-pretty) shows
fwupd-refresh.service failed
When I manually run fwupdmgr refreshit shows failed to connect to cdn.fwupd.org port 443.
Internet on both Gateway and Workstation works fine although. When I run updatecheck on Gateway, Onion Circuts app shows deb.debian.org succeeded
This issue persists on Gateway run as a user session.
Documentation didn’t help. Still need assistance. Is it a critical issue?
1 Like
That sounds like a Whonix bug; fwupd either shouldn’t be installed at all, or it should be using Tor as a proxy, but right now it looks like Whonix doesn’t configure fwupd to use Tor.
The “error” is harmless and can be safely ignored, we’ll look into fixing it.