I am using strictly and only the onion URLs of qubes-os (and the debian templates) for pulling updates.
On QubesOS Update tool, the Last Checked date for updates for debian templates is 2025-05-04, while the last dom0 update check was yesterday. This morning I manually started a total update using the same tool. No dom0 updates were detected, while the updates for debian templates failed. The logs show connection to deb.qubesos[...].onion connection failure.
Is there something wrong with the qubes-os onion URLs for updates?
Edit: here’s the logs I get from trying to update the debian template:
Updating debian-12-xfce
Refreshing package info
Refreshing packages.
Fail to refresh InRelease: tor+http://deb.qubesosfasa4zl44o4tws22di6kepyzfeqv3tg4e3ztknltfxqrymdad.onion/r4.2/vm bookworm InRelease from tor+http://deb.qubesosfasa4zl44o4tws22di6kepyzfeqv3tg4e3ztknltfxqrymdad.onion/r4.2/vm/dists/bookworm/InRelease
Fail to refresh InRelease: tor+http://deb.qubesosfasa4zl44o4tws22di6kepyzfeqv3tg4e3ztknltfxqrymdad.onion/r4.2/vm bookworm InRelease from tor+http://deb.qubesosfasa4zl44o4tws22di6kepyzfeqv3tg4e3ztknltfxqrymdad.onion/r4.2/vm/dists/bookworm/InRelease
Fail to refresh InRelease: tor+http://deb.qubesosfasa4zl44o4tws22di6kepyzfeqv3tg4e3ztknltfxqrymdad.onion/r4.2/vm bookworm InRelease from tor+http://deb.qubesosfasa4zl44o4tws22di6kepyzfeqv3tg4e3ztknltfxqrymdad.onion/r4.2/vm/dists/bookworm/InRelease
Fail to refresh InRelease: tor+http://deb.qubesosfasa4zl44o4tws22di6kepyzfeqv3tg4e3ztknltfxqrymdad.onion/r4.2/vm bookworm InRelease from tor+http://deb.qubesosfasa4zl44o4tws22di6kepyzfeqv3tg4e3ztknltfxqrymdad.onion/r4.2/vm/dists/bookworm/InRelease
Refreshed.
E:Failed to fetch tor+http://deb.qubesosfasa4zl44o4tws22di6kepyzfeqv3tg4e3ztknltfxqrymdad.onion/r4.2/vm/dists/bookworm/InRelease Connection failed [IP: 127.0.0.1 8082], E:Some index files failed to download. They have been ignored, or old ones used instead.
Hit:1 tor+http://5ajw6aqf3ep7sijnscdzw77t7xq4xjpsy335yb2wiwgouo7yfxtjlmid.onion bookworm-security InRelease
Hit:2 tor+http://2s4yqjx5ul6okpp3f2gaunr2syex5jgbfpfvhxxbbjwnrsvbk5v3qbid.onion/debian bookworm InRelease
Hit:3 https://repository.mullvad.net/deb/stable bookworm InRelease
Hit:4 tor+http://2s4yqjx5ul6okpp3f2gaunr2syex5jgbfpfvhxxbbjwnrsvbk5v3qbid.onion/debian bookworm-backports InRelease
Ign:5 tor+http://deb.qubesosfasa4zl44o4tws22di6kepyzfeqv3tg4e3ztknltfxqrymdad.onion/r4.2/vm bookworm InRelease
Ign:5 tor+http://deb.qubesosfasa4zl44o4tws22di6kepyzfeqv3tg4e3ztknltfxqrymdad.onion/r4.2/vm bookworm InRelease
Ign:5 tor+http://deb.qubesosfasa4zl44o4tws22di6kepyzfeqv3tg4e3ztknltfxqrymdad.onion/r4.2/vm bookworm InRelease
Err:5 tor+http://deb.qubesosfasa4zl44o4tws22di6kepyzfeqv3tg4e3ztknltfxqrymdad.onion/r4.2/vm bookworm InRelease
Connection failed [IP: 127.0.0.1 8082]
Reading package lists...
E: Failed to fetch tor+http://deb.qubesosfasa4zl44o4tws22di6kepyzfeqv3tg4e3ztknltfxqrymdad.onion/r4.2/vm/dists/bookworm/InRelease Connection failed [IP: 127.0.0.1 8082]
E: Some index files failed to download. They have been ignored, or old ones used instead.
How to reproduce: using the Tor Browser, navigate to https://www.qubes-os.org, then click on “.onion available” purple button on the browser “taskbar”.
This isnt a server problem - it’s yours.
The server was certainly up for the “last 10 days”, and serving Fedora,
so you should look somewhere else for the issue.
I never presume to speak for the Qubes team.
When I comment in the Forum I speak for myself.
If you look at the mirrors list. there are a number of onion mirrors that
you could use if the Qubes onion is unavailable.
I’m told that the hardware is being replaced (again),which should help
matters.
I never presume to speak for the Qubes team.
When I comment in the Forum I speak for myself.
I never changed a thing in templates or sys-whonix since I installed 4.2 or from availablity of fedora 41 templates for stable 4.2. just updated them with qubes update tool. So what can be my problem then?
Anyways it updated today for debian.
I dont know what your problem is. But it isnt (and hasnt been) the
server.
Fedora updates run fine against the onion.
NB I use a Tor proxy, and not Whonix, so your issue may lie there, but
since there havent been other users reporting the Fedora error, I’d
start by looking at your system first.
I never presume to speak for the Qubes team.
When I comment in the Forum I speak for myself.