There’s something seriously wrong here, but without more information
it’s hard to diagnose.
By contrast, on this system, Hits average around 75%, across numerous
template updates.
The only time I would expect to see results like yours would be when
the cache is being set up for the first time.
Alternatively I could imagine that this occurs if repositories are not
being correctly remapped
How did you set up this caching proxy?
How are the templates set up to use it?
What templates are you using?
Can you check the contents of /rw/bind-dirs/var/cache/apt-cacher-ng/,
and confirm that the contents cohere with /etc/var/cache/apt-cacher-ng/,
and that the largest subdirectories are remapped, like debrep, fedrep.
I never presume to speak for the Qubes team.
When I comment in the Forum I speak for myself.
I used your salt script to setup this caching proxy,
Exactly described like in your github guide like http://HTTPS
Inside /rw/bind-dirs/var/cache/apt-cache-ng/ there is indeed debrep and fedrep, There is no folder such as /etc/var/cache/apt-cacher-ng/ /var/cache/apt-cacher-ng does exist.
Debian & Fedora, commented out everything that has to do with kicksecure and whonix
It’s a bit strange because I have the same contents of apt-cacher-ng in /rw/bind-dirs/etc/apt-cacher-ng/ as in /etc/apt-cacher-ng/, Are these two locations conflicting with each other? or is that the point of bind-dirs?
Some what an improvement but why are the Requests so low?
The logging I can see the packages coming through and it works so I don’t know, what to look further for.