Ongoing DDoS attacks affecting the AUR

Support AUR
1

As most may be aware, Arch Linux is being subjected to ongoing DDoS attacks targetting their infrastructure –

This includes the Arch User Repository (AUR).

See same link for possible workarounds during service disruption :eyes:

The resulting outages have potentially dire consequences for Arch (and Arch derivative) users, and has now continued into a second month.

What does this mean for Manjaro users and the AUR?

Simply put, it means that AUR packages may fail to build.

If you experience problems updating, as a result of this situation, do not post a Support request about it, as there is little to do but wait until the AUR is again available.

Arch Linux have a service status page allowing users to monitor the AUR availability. It’s recommended that users check the status and availability of the AUR before attempting an update:

Updates fail to complete – AUR can’t be reached

Make sure to exclude the AUR, to prevent the update failing due to AUR not being available; for example, using pamac:

pamac update --no-aur
  • Avoid other “AUR helpers” such as paru, trizen or yay. :eyes:

Note: pacman is unaffected; simply update as usual:

sudo pacman -Syu

In summary:

  • Check the Arch Linux AUR status before using the AUR
  • Do not use the AUR otherwise.
  • No Support can be offered

Related:

10 Likes
9

Just a heads up that the DDoS attacks on the AUR are still happening:

As a result, DDoS protection has been enabled for aur.archlinux.org to help mitigate the ongoing disruption. While this measure helps keep the AUR website accessible, it has introduced a significant side effect: pushing to the AUR is currently not possible.

This means that AUR package maintainers cannot publish new packages, update existing ones, or fix build issues until full SSH functionality is restored.

1 Like
10

That could be an issue, as Mullvad VPN is in the AUR, not the main Manjaro Repos.

1 Like