Why does "sudo apt update" cause a series of "403 Forbidden" errors?

complete · 05-05-2022, 02:03 AM

Why does "sudo apt update" cause a series of "403 Forbidden" errors?

I have a Ubuntu 22.04 virtual machine using VMware on a Windows 10 Enterprise computer.
Part of setting things up requires I use the command:

Quote:

sudo apt update

or

Quote:

sudo apt-get update --fix-missing

both commands cause the same error messages. They consist of

Quote:

403 Forbidden [IP: 91.189.91.39 80]

Either I need to do something to establish a network connection, I assume, or I need to find a way to do what I need through downloads and file shares with the host computer. Either way, I need help.

Since I do not have the ability to share files or the clipboard memory with the Virtual Machine, I had to do a screen shot. But, fortunately, I ran that through a pretty good OCR image to text converter so I can share this:

Quote:

william@william-virtual-machine: - $ sudo apt update
[sudo] password for william:
Err:1 http://us.archive.ubuntu.com/ubuntu jammy InRelease
403 Forbidden (IP: 91.189.91.39 80]

Err:2 http://us.archive.ubuntu.com/ubuntu jammy-updates InRelease
403 Forbidden [IP: 91.189.91.39 80]

Err:3 http://us.archive.ubuntu.coR/ubuntu jammy.backports InRelease
403 Forbidden [IP: 91.189.91.39 80)

Err:4 http://securtty.ubuntu.com/ubuntu jammy-security InRelease
403 Forbidden [IP: 91.189.91.38 80]

Reading package lists... Done
N: See apt-secure(8) manpage for reposttory creatton and user conftguration detatls.
N: Updating from such a reposttory can't be done securely, and ts therefore disabled by default.
E: The reposttory 'http://us.archive.ubuntu.coR/ubuntu jammy InRelease' ts no longer signed.
E: Failed to fetch http://us.archive.ubuntu.com/ubuntu/...army/InRelease 403 Forbidden [IP: 91.189.91.39 80]
N: See apt-secure(8) manpage for repository creation and user configuration detalls.
N: Updating from such a reposttory can't be done securely, and is therefore disabled by default.
E: The repository 'http://us.archive.ubuntu.com/ubuntu jammy-updates InRelease' is no longer stgned.
E: Failed to fetch http://us.archive.ubuntu.com/ubuntu/...ates/InRelease 403 Forbtdden [IP: 91.189.91.39 80)
E: Failed to fetch http://us.archive.ubuntu.com/ubuntu/...orts/InRelease 403 Forbtdden [IP: 91.189.91.39 80]
E: The repository 'http://us.archive.ubuntu.com/ubuntu jarmy-backports InRelease' is no longer signed.
N: Updating from such a reposttory can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for reposttory creation and user configuration detalls.
E: Falled to fetch http://security.ubuntu.com/ubuntu/di...rtty/InRelease 483 Forbidden [IP: 91.189.91.38 80 ]
E: The repository 'http://security.ubuntu.com/ubuntu jammy-securtty InRelease' is no longer signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for reposttory creation and user configuration detalls.

william@william-virtual-machine:

And here is a link to the screen capture

https://photos.app.goo.gl/7cK5hYeKHFwyr5ne6

Please help. Is there some sort of configuration I need to do in order to establish network connectivity? I did a search online and so far the information regarding a 403 error is in regard to a web server files not having the proper file permissions for a browser. What changes do I need to make on my end?

pan64 · 05-05-2022, 02:30 AM

you can try it in a browser (and the other urls too): http://us.archive.ubuntu.com/ubuntu

does it work for you?

Pentium4User · 05-05-2022, 11:28 PM

Maybe check again in some hours, it is maybe a problem with the repository.
Do you (or your sysadmins) operate a application layer firewall or a proxy server?
If so, contact them and find out if these are the problem.
You can switch to the main mirror, just remove the us from the URL in sources.list.

ondoho · 05-07-2022, 01:25 AM

Quote:

Originally Posted by complete

Since I do not have the ability to share files or the clipboard memory with the Virtual Machine, I had to do a screen shot. But, fortunately, I ran that through a pretty good OCR image to text converter so I can share this:

Thank you for doing that! After replacing a few odd characters I had no problems connecting to some of these links.
Does the problem persist for you? Are you using TOR to connect?

teckk · 05-07-2022, 10:00 AM

Quote:

E: Failed to fetch http://us.archive.ubuntu.com/ubuntu/...army/InRelease 403 Forbidden [IP: 91.189.91.39 80]

I get a 404 error on that too.
http://us.archive.ubuntu.com/ubuntu/...army/InRelease

Should be this
http://us.archive.ubuntu.com/ubuntu/dists/jammy/
http://us.archive.ubuntu.com/ubuntu/...ammy/InRelease
http://us.archive.ubuntu.com/ubuntu/ubuntu/dists/jammy/
http://us.archive.ubuntu.com/ubuntu/...ammy/InRelease

Code:

whois 91.189.91.39
...
inetnum:        91.189.88.0 - 91.189.95.255
netname:        CANONICAL-CORE
country:        GB
org:            ORG-CGL14-RIPE

curl -LI http://us.archive.ubuntu.com/ubuntu/dists/jammy/
HTTP/1.1 200 OK
Date: Sat, 07 May 2022 14:57:45 GMT
Server: Apache/2.4.29 (Ubuntu)
Content-Type: text/html;charset=UTF-8

ping -c1 us.archive.ubuntu.com
PING us.archive.ubuntu.com (91.189.91.38) 56(84) bytes of data.
64 bytes from banjo.canonical.com (91.189.91.38): icmp_seq=1 ttl=50 time=31.5 ms

--- us.archive.ubuntu.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 31.456/31.456/31.456/0.000 ms

pan64 · 05-07-2022, 10:58 AM

currently two links are dead for me. Another mirror should be used.

yancek · 05-07-2022, 12:28 PM

The third link posted in post #1 is incorrect, a typo? It shows:

Quote:

http://us.archive.ubuntu.cor/ubuntu

when it should be:

Quote:

http://us.archive.ubuntu.com/ubuntu

Don't know how that would happen as the r key is not close to the m, at least on my keyboard.

The first link in the sources list is also incorrect as it shows "jarmy' rather than 'jammy'.

pan64 · 05-07-2022, 01:21 PM

Quote:

Originally Posted by yancek

Don't know how that would happen as the r key is not close to the m, at least on my keyboard.

The first link in the sources list is also incorrect as it shows "jarmy' rather than 'jammy'.

That is a screenshot and an OCR, that's why.