Sunday, April 28, 2024
 Popular · Latest · Hot · Upcoming
14
rated 0 times [  14] [ 0]  / answers: 1 / hits: 9644  / 2 Years ago, sun, may 8, 2022, 6:37:01

I've noticed that running apt-get update recently has resulted in quite a few ppa's returning "403 Forbidden". In and effort to clean them up I had a look:



W: Failed to fetch http://ppa.launchpad.net/gnome3-team/gnome3/ubuntu/dists/raring/main/binary-amd64/Packages  403  Forbidden

W: Failed to fetch http://ppa.launchpad.net/gnome3-team/gnome3/ubuntu/dists/raring/main/binary-i386/Packages 403 Forbidden

E: Some index files failed to download. They have been ignored, or old ones used instead.


The strange things is, if I copy these URLs into my browser I can access the files just fine. Why would apt-get report "403 Forbidden" if they're still accessible? I tried re-adding the ppa through add-apt-repository which downloads the signing key again, and it still reported "403 Forbidden".


More From » apt

 Answers
2

So it turns out this is an issue with squid-deb-proxy. Unfortunately it doesn't add PPAs and other repositories and just fails with an rather unexpected 403 error.



You can fix this by adding the repositories to the config file:



/etc/squid-deb-proxy/mirror-dstdomain.acl



# launchpad personal package archives (disabled by default) 
ppa.launchpad.net
private-ppa.launchpad.net


Of course, uninstalling squid-deb-proxy also works around the issue:



apt-get remove squid-deb-proxy

[#30913] Monday, May 9, 2022, 2 Years  [reply] [flag answer]
Only authorized users can answer the question. Please sign in first, or register a free account.
altybol

Total Points: 364
Total Questions: 138
Total Answers: 121

Location: France
Member since Thu, May 6, 2021
3 Years ago
altybol questions
;