I’m using Qubes OS 4.2 and I have cacher qube based on debian-11-minimal template that use sys-whonix as netvm and debian templates are updating without a problem using this cahcher and onion repos.
Now I’ve created a new cacher qube based on debian-12-minimal template that use sys-whonix as netvm and debian templates can’t update using this cahcher and onion repos but works with clearnet repos.
I’m getting this error in debian template when I try to update it:
Ign:1 http://2s4yqjx5ul6okpp3f2gaunr2syex5jgbfpfvhxxbbjwnrsvbk5v3qbid.onion/debian bookworm InRelease
Err:1 http://2s4yqjx5ul6okpp3f2gaunr2syex5jgbfpfvhxxbbjwnrsvbk5v3qbid.onion/debian bookworm InRelease
503 Host not found [IP: 127.0.0.1 8082]
E: Failed to fetch http://2s4yqjx5ul6okpp3f2gaunr2syex5jgbfpfvhxxbbjwnrsvbk5v3qbid.onion/debian/dists/bookworm/InRelease 503 Host not found [IP: 127.0.0.1 8082]
I’ve noticed that in debian-12 appvm you can’t use onion repos in sources.list without tor+anymore while it works in appvms based on debian-11 template (it’s not working for debian-11 as well and now I’m not sure that my memory is correct and if it even worked before):
Err:8 http://2s4yqjx5ul6okpp3f2gaunr2syex5jgbfpfvhxxbbjwnrsvbk5v3qbid.onion/debian bookworm Release
Direct connection to .onion domains is blocked by default. If you meant to use Tor remember to use tor+http instead of http.
With Acquire::BlockDotOnion "false"; in apt config it’s starting to work again:
Maybe the default BlockDotOnion value was changed from false to true.
I don’t know if it’s related to this issue or not, maybe apt-cacher-ng now also has BlockDotOnion value set false and it’s causing this issue.
Did anyone succeed in using apt-cacher-ng in qube based on debian-12-minimal with onion repos?
Seems to be a problem with apt-cacher-ng version, because after installing apt-cacher-ng 3.7.4 from bullseye-backports in working cacher debian-11-minimal template it’s starting to fail in the same way.
Likewise, I’m using apt-cacher-ng version 3.6.4-1 (in Whonix 16, Debian oldstable repo). If reverting to that version works for you, please mark it as the solution for others who may run into the same problem.
Reverting the version back is not a proper fix to this problem, it’s just a temporary workaround. I’ll try to build apt-cacher-ng versions between 3.6.4 and 3.7.4 to find the cause of this issue and a possible proper fix to it.