You don't say which version you are running, there have been a lot of subtle issues with the adoption that I've fixed and the 0.10.4 release has been running really, really well for me. If you ARE running 0.10.4, LMK and we can do further debugging.
https://github.com/linsomniac/apt-cacher-ultra/releases/tag/0.10.4 I'd also start over with a new cache directory (save the "ca" sub-directory): systemctl stop apt-cacher-ultra cd /var/cache/apt-cacher-ultra rm -rf cache* pool staging tmp # update your package systemctl start apt-cacher-ultra Thanks for providing the feedback. I'm considering the 0.10.4 to be a RC2 for the 1.0 release. I found an issue with expiry of "fat" repos (repos that list all historic versions of a package, docker and elastic both do this) that I put some changes in for and I want to let those soak for a while. I'd appreciate it if you gave 0.10.4 a try and let me know how it works for you. Sean On Mon, Jun 29, 2026 at 7:30 AM Anssi Saari < [email protected]> wrote: > Sean Reifschneider <[email protected]> writes: > > > In my testing, it's still very on track for a mid June 1.0 release. > I've run > > thousands of system installs and thousands of apt update/upgrade cycles > > and the issues I've run into have been addressed, 0.9.7 has been working > > great with no adoption failures (the biggest issue I'd been running > into; the > > adoption is the trickiest part but also the most worthwhile WRT surviving > > DDoS). > > Well, in my little home network this was working but after a while I > noticed unattended-updates hadn't updated and I got this with manual: > > # apt update > Get:1 https://security.debian.org/debian-security bookworm-security > InRelease [48.0 kB] > Get:2 https://deb.debian.org/debian bookworm InRelease [151 kB] > Reading package lists... Done > E: Release file for > > https://security.debian.org/debian-security/dists/bookworm-security/InRelease > is expired (invalid since 9d 10h 37min 0s). Updates for this repository > will not be applied. > > Disabling the cache and running apt update fixed it but what could cause > this? > >
