Work around an Omarchy mirror outage returning TLS errors or 404s
The cause is verified exactly: default/pacman/mirrorlist-stable in master contains the single line Server = https://stable-mirror.omarchy.org/$repo/os/$arch, and pacman-stable.conf carries [omarchy] / SigLevel = Optional TrustAll / Server = https://pkgs.omarchy.org/stable/$arch. What is missing is the consequence: Omarchy's stable channel is a pinned snapshot, so repointing core/extra/multilib at rolling Arch mirrors pulls packages *newer* than the snapshot the [omarchy] repo was built against, and the restore step (omarchy-refresh-pacman stable, which really does run pacman -Syyuu --noconfirm) then has to downgrade them all again, a messy state to land in for what is often a transient CDN error. The fix also needs -Syy after a mirror change, and -uu should not be used on the way out.
Running Omarchy packages against pure Arch mirrors mixes epochs: omarchy-refresh-pacman finishes with pacman -Syyuu, which will force-DOWNGRADE anything newer than Omarchy's mirror offers. Snapshot first (omarchy-snapshot create) if you have snapper/limine set up. Disabling the [omarchy] repo while installed omarchy-* packages remain will also make them show as orphaned/foreign until you re-enable it.
Symptom
On Omarchy only, updates fail against Omarchy's own servers:
error: failed retrieving file 'chromium-143.0.7499.192-1-x86_64.pkg.tar.zst' from stable-mirror.omarchy.org : TLS connect error: error:0A000126:SSL routines::unexpected eof while reading
or
error: failed retrieving file 'sshfs-3.7.3-3-x86_64.pkg.tar.zst.sig' from stable-mirror.omarchy.org : Exceeded the maximum allowed file size (16384) with 16384 bytes
or error: failed retrieving file 'visual-studio-code-bin-...pkg.tar.zst' from pkgs.omarchy.org : The requested URL returned error: 404.
Cause
Omarchy ships a single-server mirrorlist (Server = https://stable-mirror.omarchy.org/$repo/os/$arch) plus its own [omarchy] repo at https://pkgs.omarchy.org/stable/$arch. There is no mirror redundancy, so any CDN/TLS glitch, stale sync, or missing artefact on Omarchy's side stops all updates for everyone.
Fix
A TLS 'unexpected eof' or a one-off 404 is usually transient. Retry once before changing any config:
sudo pacman -Syu
Only if the outage persists, temporarily point core/extra/multilib at official Arch mirrors. **Understand the trade-off first:** Omarchy's stable channel is a pinned snapshot. Rolling Arch mirrors are ahead of it, so this pulls packages newer than the ones the [omarchy] repo was built against, and restoring will have to downgrade them. Treat it as a short-lived workaround.
sudo cp /etc/pacman.d/mirrorlist /etc/pacman.d/mirrorlist.omarchy
sudo tee /etc/pacman.d/mirrorlist >/dev/null <<'EOF'
Server = https://geo.mirror.pkgbuild.com/$repo/os/$arch
EOF
sudo pacman -Syyu # -Syy is required after a mirror change; keep a single -u
If it is specifically pkgs.omarchy.org (the [omarchy] repo) 404ing, leave the mirrorlist alone and comment that repo out in /etc/pacman.conf for the duration:
#[omarchy]
#SigLevel = Optional TrustAll
#Server = https://pkgs.omarchy.org/stable/$arch
When Omarchy's servers are healthy again, restore the shipped configuration:
omarchy-refresh-pacman stable
This copies /etc/pacman.conf and /etc/pacman.d/mirrorlist to .bak (overwriting any previous .bak), rewrites both from Omarchy defaults, then runs pacman -Syyuu. The -uu is what downgrades anything you pulled ahead of the snapshot, so expect a large transaction and read it before confirming.
Verify
sudo pacman -Syu completes with no retrieval errors. After omarchy-refresh-pacman stable, grep Server /etc/pacman.d/mirrorlist shows stable-mirror.omarchy.org again.
Sources
- https://github.com/basecamp/omarchy/issues/4384
- https://github.com/basecamp/omarchy/issues/5083
- https://github.com/basecamp/omarchy/issues/6191
- https://raw.githubusercontent.com/basecamp/omarchy/master/default/pacman/pacman-stable.conf
- https://raw.githubusercontent.com/basecamp/omarchy/master/bin/omarchy-refresh-pacman