You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We look to http://azure.archive.ubuntu.com/ and upon testing the connection it works fine. This is because azure.archive is allowlisted in our firewall rules. As a result it's a tad difficult to try other hosts since we'd then need to add them to our firewall.
Our sources.list file looks like
deb https://jfrog.aaw.cloud.statcan.ca/artifactory/cae-debian trusty main
deb [trusted=yes] https://jfrog.aaw.cloud.statcan.ca/artifactory/cae-debian trusty main
and using that we get
Ign:7 https://jfrog.aaw.cloud.statcan.ca/artifactory/cae-debian trusty/main amd64 c-n-f Metadata
Reading package lists... Done
E: Failed to fetch https://jfrog.aaw.cloud.statcan.ca/artifactory/cae-debian/dists/trusty/main/binary-amd64/Packages 404 Not Found [IP: ... 443]
E: Some index files failed to download. They have been ignored, or old ones used instead.
We tried using the cloud main ubuntu repo because it seems like the azure repo has intermittent errors 12 which makes it difficult to use.
That attempt also seems to have ended in failure receiving the same errors as our aaw artifactory however.
The text was updated successfully, but these errors were encountered:
I followed the suggestions here to make Metadata Retrieval Cache Period and Missed Retrieval Cache Period 0 and turned on Bypass HEAD requests as I saw that in another possible solution
This is for our debian repo;
cae-debian
We look to http://azure.archive.ubuntu.com/ and upon testing the connection it works fine. This is because azure.archive is allowlisted in our firewall rules. As a result it's a tad difficult to try other hosts since we'd then need to add them to our firewall.
Our
sources.list
file looks likeand using that we get
We tried using the cloud main ubuntu repo because it seems like the azure repo has intermittent errors 1 2 which makes it difficult to use.
That attempt also seems to have ended in failure receiving the same errors as our aaw artifactory however.
The text was updated successfully, but these errors were encountered: