For some reason when I attempt to update my templates with the Qubes Updater I get this error:
Updating fedora-39-xfce
Refreshing package info
Errors during downloading metadata for repository 'fedora':
- Curl error (56): Failure when receiving data from the peer for https://mirrors.fedoraproject.org/metalink?repo=fedora-39&arch=x86_64 [Proxy CONNECT aborted]
- Curl error (56): Failure when receiving data from the peer for https://mirrors.fedoraproject.org/metalink?repo=fedora-39&arch=x86_64&countme=1 [Proxy CONNECT aborted]
Failed to download metadata for repo 'fedora': Cannot prepare internal mirrorlist: Curl error (56): Failure when receiving data from the peer for https://mirrors.fedoraproject.org/metalink?repo=fedora-39&arch=x86_64 [Proxy CONNECT aborted]
Error: Failed to download metadata for repo 'fedora': Cannot prepare internal mirrorlist: Curl error (56): Failure when receiving data from the peer for https://mirrors.fedoraproject.org/metalink?repo=fedora-39&arch=x86_64 [Proxy CONNECT aborted]
I also was trying to update my fedora-39 template to fedora-41 via this guide And after running sudo dnf --releasever=41 distro-sync --best --allowerasing
in the fedora template, I get this error as well:
Fedora 41 - x86_64 0.0 B/s | 0 B 00:01
Errors during downloading metadata for repository 'fedora':
- Curl error (56): Failure when receiving data from the peer for https://mirrors.fedoraproject.org/metalink?repo=fedora-41&arch=x86_64 [Proxy CONNECT aborted]
Error: Failed to download metadata for repo 'fedora': Cannot prepare internal mirrorlist: Curl error (56): Failure when receiving data from the peer for https://mirrors.fedoraproject.org/metalink?repo=fedora-41&arch=x86_64 [Proxy CONNECT aborted]
I tried several things mentioned in similar issues like this and this. But nothing has worked. I also installed fedora-39-xfce from Qubes Template Manager, and made it the new sys-net template, but that didn’t fix it either.
Any help would be much appreciated. Thanks!
You certainly have a problem with the qube used as a proxy by templates to reach the Internet, I think the default is sys-net or sys-firewall, you can find what qube is used for this role in the GUI “Qubes OS global config” in the “Updates” tab, you will find a line “Default update proxy”.
Open the settings of the qube you found in “default update proxy”, go in “Services” tab and make sure “qubes-updates-proxy” exists and is checked. Restart that qube to be sure it’s fine.
In that qube, you can ensure the service is really running using the following command:
sudo systemctl status qubes-updates-proxy
The output of a working service should look like this:
[user@sys-firewall ~]$ sudo systemctl status qubes-updates-proxy
â—Ź qubes-updates-proxy.service - Qubes updates proxy (tinyproxy)
Loaded: loaded (/usr/lib/systemd/system/qubes-updates-proxy.service; enabled; preset: enabled)
Drop-In: /usr/lib/systemd/system/service.d
└─10-timeout-abort.conf
Active: active (running) since Sat 2025-01-11 09:27:42 CET; 22min ago
Main PID: 570 (tinyproxy)
Tasks: 1 (limit: 7680)
Memory: 1.6M (peak: 1.9M)
CPU: 8ms
CGroup: /system.slice/qubes-updates-proxy.service
└─570 /usr/bin/tinyproxy -d -c /etc/tinyproxy/tinyproxy-updates.conf
janv. 11 09:27:42 sys-firewall systemd[1]: Started qubes-updates-proxy.service - Qubes updates proxy (tinyproxy).
janv. 11 09:27:42 sys-firewall tinyproxy-wrapper[570]: Found tinyproxy at /usr/bin/tinyproxy
janv. 11 09:27:42 sys-firewall tinyproxy-wrapper[570]: WARNING: obsolete config item on line 14
janv. 11 09:27:42 sys-firewall tinyproxy-wrapper[570]: WARNING: obsolete config item on line 15
janv. 11 09:27:42 sys-firewall tinyproxy-wrapper[570]: WARNING: obsolete config item on line 16
janv. 11 09:27:42 sys-firewall tinyproxy-wrapper[570]: WARNING: obsolete config item on line 17
janv. 11 09:27:42 sys-firewall tinyproxy[570]: Initializing tinyproxy ...
janv. 11 09:27:42 sys-firewall tinyproxy[570]: Reloading config file (/etc/tinyproxy/tinyproxy-updates.conf)
janv. 11 09:27:42 sys-firewall tinyproxy[570]: Reloading config file finished
Thank you! this whole time I was trying to apply fixes to sys-net when it was really the fault of sys-firewall . I should have checked the global config way sooner. It is all working now. Thanks for the help.