Log in Sign up
Reliable repository access for servers in Iran

Linux repositories for servers in Iran; current, secure, and accessible

Sanctions and access restrictions can interrupt package installation and updates on servers in Iran. FluxCDN provides an accessible route to original Linux and developer packages while keeping content, releases, and upstream signatures intact.

Browse repositoriesChoose distribution and release
Secure package route availablemirror.fluxcdn.cloud

Original package with upstream signature verificationsudo apt update

Find the repository you need

Search for an operating system, database, or tool. Each result opens a complete guide without sending you to a raw repository URL.

52paths in this list

Linux distributions

15

Databases and messaging

7

Development and CI/CD

13

Infrastructure and networking

9

Web, observability, and search

8

FluxCDN base URL
  1. Identify release and channelRead the operating-system release, architecture, and active channel from the current configuration.
  2. Change only the base URLKeep the remaining path, suite, components, and signing key exactly as documented upstream.
  3. Verify the active sourceRefresh package metadata and confirm that your package manager reports the FluxCDN domain.

Check the release and final configuration

Keep GPG and package signature verification enabled, and back up the current source file before editing it.

Docker packages and Docker images are different

Use the package repository to install Docker Engine. For public Docker Hub images, add the separate FluxCDN Registry Mirror to Docker.

Open the Docker Mirror guide
Install Docker Enginemirror.fluxcdn.cloud/docker

deb and rpm packages for Docker CE, CLI, Buildx, and Compose.

Pull container imagesregistry.fluxcdn.cloud

A mirror for pulling public Docker Hub images with normal docker pull commands.

Package management stays familiar

After selecting FluxCDN, installation and updates still use the standard tools already available on your system—without a custom client or a new workflow.

  1. Choose the distribution

    Use the prepared command that matches your operating-system release.

  2. Keep verification intact

    Preserve the original suite, architecture, components, and signing key.

  3. Install and update normally

    Continue using the package-manager commands you already know.

Back up the current repository file before any change so returning to the previous configuration remains simple.

The download address changes; the trust chain does not

Only the repository base URL changes. Keep the release, suite, architecture, components, channel, and original signing key exactly as provided upstream.

  • Original signing keyPackage authenticity remains verified by the project’s official key.
  • Encrypted transportEvery public repository path is available over HTTPS.
  • Public, read-only deliveryThe gateway serves downloads and does not accept public uploads.
Verification activeSIGNED PACKAGE
PackageSignature

Signed-ByOriginal key preserved

Before changing a repository

Short answers to the details that matter when using a repository mirror.

Do I need special software?

No. Use the standard package manager already available on your system and change only the repository address.

Should I disable GPG verification?

No. Keep the official signing key and GPG verification enabled. Disabling package authentication is not recommended.

Is the Debian security repository available?

Yes. debian-security is available as a separate path and is included with the main repository in the prepared Debian command.

How is the Docker CE repository different from Docker Registry?

Docker CE packages install Engine, CLI, Buildx, and Compose. The Registry Mirror is used to pull public Docker Hub images.

Can I upload packages?

No. Public paths are read-only and intended for package downloads.

How do I roll back?

Restore the backup created before the change, refresh package metadata, and verify the active source.

FluxCDN

Choose your distribution and enable the repository now

Choose the exact distribution release, copy the prepared command, and continue managing packages with the same familiar tools.

Choose distribution and releaseBrowse repositories

52 repository pathsOperating systems, databases, and tools

Public HTTPS accessNo proprietary client required

Upstream signaturesOriginal keys and verification stay intact

Standard package managersAPT, DNF, apk, pacman, and Zypper

Original packages, current releases, verified signatures

Access restrictions should not force you to use an untrusted package source. FluxCDN keeps the original package and its upstream verification chain available to servers in Iran.

  • Current releases and security updatesNew releases and security updates remain available through the repository path.
  • No repackaging or content changesYou receive the package published by the upstream project without content modification.
  • Upstream signature verificationYour standard package manager still verifies signatures, releases, and architecture.

Choose the distribution and release

Select the installed distribution and then its exact release to avoid mixing incompatible repository suites.

Release installed on the server

Ubuntu 24.04 and newer

The current deb822 file is backed up and the codename is read from the system.

sudo cp -a /etc/apt/sources.list.d/ubuntu.sources \
  /etc/apt/sources.list.d/ubuntu.sources.backup.$(date +%F-%H%M%S)

. /etc/os-release
CODENAME="${UBUNTU_CODENAME:-$VERSION_CODENAME}"

sudo tee /etc/apt/sources.list.d/ubuntu.sources >/dev/null <<EOF
Types: deb
URIs: https://mirror.fluxcdn.cloud/ubuntu
Suites: ${CODENAME} ${CODENAME}-updates ${CODENAME}-backports ${CODENAME}-security
Components: main restricted universe multiverse
Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg
EOF

sudo apt update
Verify the active source after running the commandThe result should show mirror.fluxcdn.cloud for the selected repository.
apt-cache policy | grep -A3 mirror.fluxcdn.cloud