How to Access Ubuntu Services When a Cyber Attack Disrupts Canonical's Websites

By • min read

Introduction

When a sustained, cross-border attack knocks out Canonical's websites—including Ubuntu.com, the Snap Store, and Launchpad—you might feel stranded. This isn't just a minor glitch; it's a real-world event that affects millions of users. The good news? Ubuntu's core infrastructure was built to withstand such disruptions. In this guide, you'll learn how to continue using Ubuntu services, manage packages, and stay informed while the attack is being mitigated. Whether you're a home user or a sysadmin, these steps will keep your system running smoothly without relying on the primary web interfaces.

What You Need

• A working computer running Ubuntu (or a derivative like Kubuntu, Xubuntu, etc.)
• Internet connection (even if Canonical's main servers are down, alternative mirrors work)
• Basic familiarity with the terminal or command line
• A list of alternative Ubuntu mirror URLs (provided in steps)
• Access to a web browser or a tool like wget or curl for manual downloads

Step-by-Step Guide

Step 1: Identify Which Services Are Affected

First, confirm what's offline. During the April 30 attack, services started going down around 6 PM UK time. Check the official Canonical status page (if accessible) or community forums like Ubuntu Discourse. Write down which specific services you need: the main Ubuntu website, Snap Store, Launchpad bug tracker, or the archive.ubuntu.com package repository. Note that the APT repositories are mirrored widely—many will remain online even if the primary server is under fire.

Step 2: Switch to a Different APT Mirror

The biggest worry is usually package updates. Since archive.ubuntu.com may be unreachable, edit your /etc/apt/sources.list file to use a different mirror. Open a terminal and run:

sudo nano /etc/apt/sources.list

Replace all occurrences of archive.ubuntu.com with a mirror that's closer to you. For example:

• US: us.archive.ubuntu.com
• UK: gb.archive.ubuntu.com
• Germany: de.archive.ubuntu.com

Alternatively, use a generic mirror like mirrors.ubuntu.com or ftp.cc.uoc.gr. Save the file and run sudo apt update to test connectivity. If that works, you can install or upgrade packages as usual.

Step 3: Download ISO Images Without the Website

Need to install Ubuntu fresh? Even if the main website is down, ISO images are available from many mirrors. Use a direct download link from a reliable mirror. For example, open a terminal and use wget:

wget http://releases.ubuntu.com/22.04/ubuntu-22.04.3-desktop-amd64.iso

If that fails, try a Canadian mirror: http://mirror.csclub.uwaterloo.ca/ubuntu-releases/22.04/. You can also use BitTorrent – the official torrent files are often mirrored. Visit an alternative status page (like the download page may be down, but direct mirror links still work).

Step 4: Use the Snap Store Command-Line Without the Web Interface

The Snap Store website may be offline, but the snap command itself can still work if it can reach a working backend. Try:

snap find vlc

If that fails, switch snap's mirror using:

sudo snap set system proxy.http=http://your-proxy:port

But before doing that, check if the snap socket is blocked. Sometimes the CDN that serves snap packages remains up even when the website is down. If search doesn't work, you can still install a known snap by ID:

sudo snap install vlc --channel=stable

If the backend call fails, wait and try again later.

Step 5: Stay Updated via Community Channels

Canonical often provides real-time updates on Twitter (@ubuntu) or on their own status page. Since the main website may be offline, follow these alternative sources:

• Ubuntu's official IRC channel on Libera.Chat (#ubuntu)
• Reddit (r/Ubuntu or r/linux)
• Discourse forum (if accessible)

Bookmark these now so you can quickly check them during an incident.

Step 6: Monitor for Updates and Return to Normal

Attacks like these are usually resolved within hours to days. Once you hear that services are restored, revert any mirror changes you made:

sudo sed -i 's|gb.archive.ubuntu.com|archive.ubuntu.com|g' /etc/apt/sources.list

Then run sudo apt update to ensure you're back on the official servers. Clear any temporary proxy settings for snap.

Tips for Smooth Operations During an Attack

• Know your mirrors: Keep a list of 2-3 reliable Ubuntu mirrors in your notes. You can find them at Launchpad's mirror list (if that site is accessible). If not, use Google to search for "Ubuntu mirrors" and find an up-to-date list.
• Use a local caching proxy: For large environments, set up apt-cacher-ng or squid to cache packages. During an outage, packages already cached remain available even if remote mirrors are down.
• Download ISOs beforehand: Keep a copy of the latest Ubuntu LTS ISO on a USB drive or local server. That way you never have to download during an emergency.
• Alternative package managers: Consider using flatpak or appimage for applications that are also distributed via Flathub or the Snap Store. These platforms have separate infrastructure.
• Check your own network: Sometimes a local DNS issue can mimic a global outage. Use dig archive.ubuntu.com or ping to see if the problem is on your end. If you get no response but other websites work, the attack is likely the cause.
• Don't panic: Canonical engineers are experienced in handling DDoS attacks. The services usually come back quickly. Avoid unnecessary changes to your system—just use the workarounds and wait for the all-clear.

Remember: the Ubuntu community is resilient. By following these steps, you can keep your system secure and up-to-date even when the main websites are under fire.