How to fix network unreachable errors and APT conflicts on Ubuntu 24.04

Anyone using Linux daily knows that running sudo apt update is the fastest health check for your operating system. When package synchronization fails, the environment stalls: you cannot install new software or apply critical security updates.

I recently encountered a double failure while updating an Ubuntu 24.04 (Noble Numbat) machine: an annoying notice about unsupported i386 architecture on a private repository, paired with a critical connection breakdown reporting connect (101: Network is unreachable) when reaching Launchpad PPAs over IPv6.

Here is how I isolated both issues, what to do when add-apt-repository crashes during removal due to network timeouts, and how to configure APT for reliable connectivity.

1. Initial diagnosis and terminal error trace#

Running the package update command:

sudo apt update

The terminal returned a mixture of notices and connection timeouts:

Reading state information... Done
1 package can be upgraded. Run 'apt list --upgradable' to see it.
N: Skipping acquisition of configured file 'main/binary-i386/Packages', as repository 'https://us-central1-apt.pkg.dev/projects/app-updater-dev app-debian InRelease' doesn't support architecture 'i386'
W: Failed to fetch https://ppa.launchpadcontent.net/cappelikan/ppa/ubuntu/dists/noble/InRelease  Could not connect to ppa.launchpadcontent.net:443 (2620:2d:4000:1::81). - connect (101: Network is unreachable) Could not connect to ppa.launchpadcontent.net:443 (185.125.190.80), connection timed out
W: Failed to fetch https://ppa.launchpadcontent.net/danielrichter2007/grub-customizer/ubuntu/dists/noble/InRelease  Could not connect to ppa.launchpadcontent.net:443 (2620:2d:4000:1::81). - connect (101: Network is unreachable)
W: Failed to fetch https://ppa.launchpadcontent.net/graphics-drivers/ppa/ubuntu/dists/noble/InRelease  Could not connect to ppa.launchpadcontent.net:443 (2620:2d:4000:1::81). - connect (101: Network is unreachable)
W: Failed to fetch https://ppa.launchpadcontent.net/obsproject/obs-studio/ubuntu/dists/noble/InRelease  Could not connect to ppa.launchpadcontent.net:443 (2620:2d:4000:1::81). - connect (101: Network is unreachable)
W: Some index files failed to download. They have been ignored, or old ones used instead.

Examining the trace revealed two unrelated causes:

1. Architecture notice (N): The private Google Artifact Registry repository only builds 64-bit packages (amd64). Because Ubuntu enables multiarch by default (often required by Wine or Steam), APT requests i386 indices that simply do not exist on the remote server.
2. Network failure (W): Multiple Launchpad PPAs failed with connect (101: Network is unreachable). The system resolved the host to an IPv6 address (2620:2d:4000:1::81), but the local or upstream network route dropped the packets, causing connection timeouts.

2. Fixing i386 architecture warnings in third-party repositories#

The repository definition inside /etc/apt/sources.list.d/app-updater.list lacked an explicit architecture constraint:

deb [signed-by=/etc/apt/keyrings/app-repo-key.gpg] https://us-central1-apt.pkg.dev/projects/app-updater-dev/ app-debian main

Without an explicit architecture declaration on a multiarch system, APT queries both binary-amd64 and binary-i386.

To suppress the warning and prevent wasted HTTP requests, add the arch=amd64 parameter:

1. Open the file in an editor:

sudo nano /etc/apt/sources.list.d/app-updater.list

1. Add arch=amd64 inside the brackets:

deb [arch=amd64 signed-by=/etc/apt/keyrings/app-repo-key.gpg] https://us-central1-apt.pkg.dev/projects/app-updater-dev/ app-debian main

1. Save and close the file.

During the next run, APT will only query 64-bit packages for this repository.

3. The add-apt-repository failure trap when network is offline#

To clean up the unreachable Launchpad PPAs, the standard approach is invoking the removal helper:

sudo add-apt-repository --remove ppa:danielrichter2007/grub-customizer

Instead of removing the configuration, the command failed with a Python exception:

Cannot add PPA: '"Failed to download the PPA: HTTPSConnectionPool(host='launchpad.net', port=443): Max retries exceeded with url: /api/1.0/~danielrichter2007/+archive/grub-customizer (Caused by NewConnectionError('<piped_id>: Failed to establish a new connection: [Errno 101] Network is unreachable'))."'.

The add-apt-repository script contacts Launchpad's REST API to validate metadata before purging local configuration. Because network traffic to Launchpad was broken, the tool exhausted its retry limit and crashed without removing anything.

4. Manual offline cleanup of broken ppas#

When higher-level tools fail due to missing network connectivity, the most effective approach is directly modifying local configuration files.

Switch to the sources directory:

cd /etc/apt/sources.list.d/
ls -la

Identify the .list files associated with unreachable or obsolete PPAs and remove them directly using rm:

sudo rm \
cappelikan-ppa-noble.list \
graphics-drivers-ppa-noble.list \
kelebek333-nvidia-legacy-noble.list \
maarten-fonville-android-studio-noble.list \
obsproject-obs-studio-noble.list

Removing these files directly stops APT from querying those endpoints on the next run, completely bypassing the external API requirement.

5. Forcing APT to use ipv4#

The 101: Network is unreachable error frequently points to misconfigured IPv6 routes or ISPs delivering broken IPv6 endpoints. When the OS prioritizes IPv6 over IPv4, queries hang until they time out.

To verify whether IPv6 was the sole problem, I ran APT with an IPv4 enforcement flag:

sudo apt update -o Acquire::ForceIPv4=true

The command completed immediately, fetching all remaining repositories (Docker, Tailscale, browsers, and official Ubuntu archives) without errors.

To make this behavior permanent across all future package operations, create a dedicated configuration snippet:

echo 'Acquire::ForceIPv4 "true";' | sudo tee /etc/apt/apt.conf.d/99force-ipv4

If you encounter similar timeouts across other services on your machine, you can also temporarily disable IPv6 at the kernel level:

sudo sysctl -w net.ipv6.conf.all.disable_ipv6=1
sudo sysctl -w net.ipv6.conf.default.disable_ipv6=1

6. Practical takeaways for package management on Ubuntu noble#

With arch=amd64 assigned, obsolete PPAs removed, and IPv4 enforced, sudo apt update returned to completing in under three seconds with zero warnings.

Key takeaways when managing packages on Ubuntu 24.04:

1. Legacy PPAs on Ubuntu Noble: Ubuntu 24.04 introduced modern system libraries that many older PPAs have not yet adapted to. Where available, prefer official upstream packages, Flatpaks, or snaps over unmaintained PPAs.
2. High-level helpers need manual fallbacks: The add-apt-repository tool is convenient, but when network connectivity drops, knowing your way around /etc/apt/sources.list.d/ saves time and avoids tool crashes.
3. Unstable IPv6 routing: If commands like ping 8.8.8.8 work normally while specific HTTPS repositories fail with error 101, suspect broken IPv6 routes and force an IPv4 fallback.

See also

Linux Dissecting the APT subsystem: deb822 duplications, idempotency, and multiarch conflicts

Linux Fixing 'cannot refresh cache whilst offline' in Linux and cPanel

DevOps Under the hood of Ansible: from static inventories to SSH multiplexing and privilege escalation

This post is licensed under CC BY-NC.