Why am I getting these error messages?

Support and Help
,
1

Ubuntu Version:
Ubuntu 24.04.4 LTS

Problem Description:
I’ve been trying to update the system packages for a few days now, and I keep getting this specific error with the security packages. Does anyone know why this is happening?

I read not long ago that Ubuntu suffered several DDoS attacks, and I don’t know if this is related to that or not. I have zero knowledge of these topics in general, so I apologize in advance if my question is dumb.

Thank you very much!

Relevant System Information:

Hardware Information:

  • Hardware Model: ASUSTeK COMPUTER INC. P8B75-M
  • Memory: 24.0 GiB
  • Processor: Intel® Core™ i5-2500 × 4
  • Graphics: NVIDIA GeForce GT 1030
  • Disk Capacity: 1.5 TB

Software Information:

  • Firmware Version: 1701
  • OS Name: Ubuntu 24.04.4 LTS
  • OS Build: (null)
  • OS Type: 64-bit
  • GNOME Version: 46
  • Windowing System: Wayland
  • Kernel Version: Linux 6.17.0-23-generic

Screenshots or Error Messages:

facundo@Fubuntu:~$ sudo apt update
[sudo] password for facundo:
Get:1 https://esm.ubuntu.com/apps/ubuntu noble-apps-security InRelease [8,371 B]
Get:2 https://esm.ubuntu.com/apps/ubuntu noble-apps-updates InRelease [8,220 B]
Get:3 https://esm.ubuntu.com/infra/ubuntu noble-infra-security InRelease
Get:4 https://esm.ubuntu.com/infra/ubuntu noble-infra-updates InRelease [8,213 B]
Get:5 http://security.ubuntu.com/ubuntu noble-security InRelease [126 kB]
...
Ign:28 http://security.ubuntu.com/ubuntu noble-security/main Translation-en 
Ign:29 http://security.ubuntu.com/ubuntu noble-security/main amd64 Components
Err:26 http://security.ubuntu.com/ubuntu noble-security/main i386 Packages
  Connection timed out IP: 185.125.190.81 80]
Err:28 http://security.ubuntu.com/ubuntu noble-security/main Translation-en
  Connection failed IP: 91.189.91.83 80]
Err:29 http://security.ubuntu.com/ubuntu noble-security/main amd64 Components
  Connection failed [IP: 185.125.190.83 80]
Fetched 12.2 MB in 6min 5s (33.6 kB/s)
Reading package lists... Done Building dependency tree... Done Reading state information... Done
5 packages can be upgraded. Run 'apt list --upgradable' to see them.
W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/noble-security/main/binary-i386/Packages Connection timed out [IP: 185.125.190.81 80]
W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/noble-security/main/i18n/Translation-en Connection failed [IP: 91.189.91.83 80]
W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/noble-security/main/dep11/Components-amd64.yml Connection failed TIP: 185.125.190.83 80]
W: Some index files failed to download. They have been ignored, or old ones used instead.

What I’ve Tried:

sudo apt update

2

If you were to hazard a guess, what would it be?

3

In your second screenshot, I see “Connection timed out” errors for security.ubuntu.com. These types of errors are directly tied to network connections & availability, and I have to warrant this is a result of the DDOS impacting Canonical’s servers.

I have seen a couple of threads stating canonical/launchpad/etc server availability is hit-and-miss, but I haven’t seen an official statement (yet) regarding full availability.

Relevant thread with corresponding spin-offs: Update concerning DDOS attack on Canonical and Ubuntu

4 Likes
4

This usually isn’t related to DDoS, it’s more likely a repo or cache issue.

Try these steps:



sudo apt clean
sudo apt update --fix-missing
sudo dpkg --configure -a
sudo apt upgrade

If it still fails, check your sources list or switch to another mirror (sometimes the server you’re using is out of sync).

Also make sure your internet/DNS is working fine.

1 Like
5

That “Connection timed out” message at the bottom of the second image indicates a network connectivity issue. A network issue caused by an ongoing DDoS. Recommending users to run apt update again will only add to network load the archives are under. It’s won’t solve anything for the OP and will just perpetuate the problem on Canonical’s end.

3 Likes
6

This topic was automatically closed 18 hours after the last reply. New replies are no longer allowed.