Hi again.
I wanted to revisit this to see if anything might’ve changed in the past few months.
I made sure the fedora TemplateVM had the appropriate qvm-tag to use my apt-cacher-ng VM for updates and that my fedora repo URLs had the http://HTTPS/// prefix.
While dnf update -y received the occasional and expected 503 errors, they eventually went away and were replaced with several consistent curl error 56s and 18s (sample of each below):
Curl error (56): Failure when receiving data from the peer for https://fedora.ip-connect.vn.ua/linux/releases/41/Everything/x86_64/os/repodata/repomd.xml [CONNECT tunnel failed, response 403] - https://fedora.ip-connect.vn.ua/linux/releases/41/Everything/x86_64/os/repodata/repomd.xml - repomd.xml
Curl error (18): Transferred a partial file for http://fedora.ip-connect.vn.ua/linux/releases/41/Everything/x86_64/os/repodata/repomd.xml [end of response with 150 bytes missing] - http://fedora.ip-connect.vn.ua/linux/releases/41/Everything/x86_64/os/repodata/repomd.xml - repomd.xml
I verified these URLs were valid in my browser.
I double-checked that the cacher repo mod command didn’t miss anything in the /etc/yum.repos.d/ directory
grep -Flr "https://" /etc/yum.repos.d/ 2>&1
The failing URLs are coming from somewhere else–maybe the .xml files?
I tried to troubleshoot the curl errors by creating a /root/.curlrc file with
proxy=http://127.0.0.1:8082
Deleted this when it had no affect.
I also attempted various permutations of http/s proxies (to no avail):
export http_proxy=http://127.0.0.1:8082
export https_proxy=https://127.0.0.1:8082
export https_proxy=http://127.0.0.1:8082
Found Setting up a cache server for apt packages which mentioned configuring the PassThroughPattern attribute in template-cacher’s /etc/apt-cacher-ng/acng.conf and so I added a wide-open config here
PassThroughPattern: .*
This also had no affect.
I saw @unman mentioned enabling “extended fedora repository lists” in
Fedora 39 Errors during downloading metadata for repository 'fedora': - Status code: 500 - #5 by unman, but I’m not sure if that would affect these curl errors I’ve been trying to research and troubleshoot.
Any thoughts?