This is the error I get when trying to update (none of the updates, Fedora or Debian, succeed, and it seems like a general internet proxy error):
Error on updating fedora-33: Command ‘[‘sudo’, ‘qubesctl’, ‘–skip-dom0’, ‘–targets=fedora-33’, ‘–show-output’, ‘state.sls’, ‘update.qubes-vm’]’ returned non-zero exit status 20
ID: /usr/lib/rpm/macros.d/macros.qubes Function: file.managed Result: True Comment: File /usr/lib/rpm/macros.d/macros.qubes is in the correct state Started: 07:44:12.190060 Duration: 57.508 ms Changes:
ID: dnf-makecache Function: cmd.script Result: False Comment: Could not create DNF metadata cache Started: 07:44:12.341574 Duration: 5421.316 ms Changes:
ID: update Function: pkg.uptodate Result: False Comment: One or more requisite failed: update.qubes-vm.dnf-makecache Started: 07:44:23.989928 Duration: 0.014 ms Changes:
ID: notify-updates Function: cmd.run Name: /usr/lib/qubes/upgrades-status-notify Result: False Comment: Command "/usr/lib/qubes/upgrades-status-notify" run Started: 07:44:23.990119 Duration: 9916.293 ms Changes: ---------- pid: 979 retcode: 1 stderr: Error: Failed to download metadata for repo 'updates': Cannot prepare internal mirrorlist: Curl error (56): Failure when receiving data from the peer for https://mirrors.fedoraproject.org/metalink?repo=updates-released-f33&arch=x86_64 [Proxy CONNECT aborted] stdout:
Total states run: 4
Total run time: 15.395 s
I assume the most important part from that is “Proxy CONNECT aborted”? I had similar issues with my Debian templates, and the most relevant part from that seems to be:
Reading from proxy failed - read (11: Resource temporarily unavailable) [IP: 127.0.0.1 8082]
If possible (and if the answer isn’t a simple, “oh, we know about that and will fix it soon”), can you tell me how to troubleshoot these proxy errors? Here’s what is already in my arsenal, please add more tools to it:
- I looked up the qubes.UpdatesProxy since someone previously helped me find that file. (whonix updates succeeded just now after fixing the vm name in that file). The other entry still says:
$type:TemplateVM $default allow,target=sysFirewall
- I ran a ping in sysFirewall before running the updater, and the ping succeeded.
- I tried restarting the relevant Qubes, to no avail.