Comment 17 for bug 1960264

I've just seen the same bug with jammy and apt-cacher-ng 3.7.4-1build1

A simple "sudo systemctl restart apt-cacher-ng" fixed it.

========

First try:

$ sudo apt-get update
...
Reading package lists... Done
E: Failed to fetch http://gb.archive.ubuntu.com/ubuntu/dists/jammy-security/restricted/cnf/Commands-amd64 503 Connection closed, check DlMaxRetries [IP: 127.0.0.1 3142]
W: Failed to fetch http://gb.archive.ubuntu.com/ubuntu/dists/jammy-security/universe/binary-amd64/Packages.gz 503 Connection closed, check DlMaxRetries [IP: 127.0.0.1 3142]
W: Failed to fetch http://gb.archive.ubuntu.com/ubuntu/dists/jammy-security/universe/i18n/Translation-en.gz 503 Connection closed, check DlMaxRetries [IP: 127.0.0.1 3142]
W: Failed to fetch http://gb.archive.ubuntu.com/ubuntu/dists/jammy-security/multiverse/binary-amd64/Packages.gz 503 Connection closed, check DlMaxRetries [IP: 127.0.0.1 3142]
W: Some index files failed to download. They have been ignored, or old ones used instead.

Then:

$ sudo systemctl restart apt-cacher-ng
$ sudo apt-get update
...
Reading package lists... Done
$