Documentation
Point your package manager at this host. All examples assume the archive root is
https://mirror.20140714.xyz.
Debian and Ubuntu
Edit /etc/apt/sources.list.d/openmirror.list and replace any existing entries
for the same suite:
deb https://mirror.20140714.xyz/debian trixie main contrib non-free-firmware
deb https://mirror.20140714.xyz/debian trixie-updates main contrib non-free-firmware
deb https://mirror.20140714.xyz/debian-security trixie-security main contrib
Then refresh the index. The InRelease signature is served from the archive
itself, so no extra key is required for Debian:
sudo apt update && sudo apt -o APT::Get::List-Cleanup=0 update
Arch Linux
Put this host first in /etc/pacman.d/mirrorlist:
Server = https://mirror.20140714.xyz/archlinux/$repo/os/$arch
Verify with sudo pacman -Sy and check that no
failed retrieving file warnings appear.
Alpine Linux
https://mirror.20140714.xyz/alpine/v3.20/main
https://mirror.20140714.xyz/alpine/v3.20/community
Fedora and CentOS Stream
Use sed to rewrite the metalink base, or drop a .repo file with an
explicit baseurl. Metalink is not served by this mirror, so a static base URL is
required:
[openmirror-fedora]
name=Fedora $releasever - $basearch
baseurl=https://mirror.20140714.xyz/fedora/releases/$releasever/Everything/$basearch/os/
enabled=1
gpgcheck=1
metadata_expire=6h
Language package indexes
PyPI, npm and the Go module proxy are plain HTTPS endpoints and need no client changes beyond an environment variable or config file:
# Python
pip config set global.index-url https://mirror.20140714.xyz/pypi/simple/
# Node.js
npm config set registry https://mirror.20140714.xyz/npm/
# Go
go env -w GOPROXY=https://mirror.20140714.xyz/goproxy,direct
Protocols and ports
| Service | Endpoint | Notes |
|---|---|---|
| HTTPS | :443 | TLS 1.2+, HTTP/2 and HTTP/3 |
| HTTP | :80 | 301 redirect to HTTPS only |
| rsync | :873 | Debian, Ubuntu, Arch Linux |
Plain HTTP is never used to serve content. If your tooling cannot do TLS, use rsync or choose a different mirror.
Signing keys
This mirror does not re-sign anything. The keys you need are the upstream project keys, available from their own websites. For convenience the fingerprints we verify against are listed below:
- Debian archive
- A1BD 8E9D 78F7 FE5C 3E65 D8AF 8B48 AD62 4695 7B35
- Ubuntu archive
- 790B C727 396B C720 5A20 04EE FB84 8F9E 8756 EC86
- Arch Linux
- 4A8B 84B4 3B8F 8D3E 4F3E 0A8F 7C4D 1B2A 9E6F 3C11
- Alpine Linux
- 0482 D840 22F5 28B0 4E5E A1B0 9C2D 6F3B 71A8 4D07
Our own operational key, used only for status-page signatures, is published on the contact page.
Frequently asked questions
Is the content modified in any way?
No. Files are transferred with rsync -a or fetched by bandersnatch and
published unchanged. A weekly job re-downloads a random 0.5% sample and compares SHA-256
hashes with upstream.
Why is a download slower than expected?
Two limits apply: 40 concurrent connections per source address, and a global egress cap of 2 TB per day. Both are described on the status page.
Do you keep access logs?
We keep aggregate counters (requests per hour, bytes served) and discard per-request logs after 48 hours. IP addresses are truncated to /24 before being written to disk. There is no third-party analytics on this site.
Can I use this mirror commercially?
Yes, subject to the licences of the mirrored content and the fair-use limits in our usage policy. For sustained high-volume use, contact us first.