Linux Packages Repository FAQ

You will likely find an answer to your question here. The GetPageSpeed repository ships signed RPM packages for RHEL and its derivatives, Amazon Linux and Fedora, and signed APT packages for Debian and Ubuntu, from one subscription.

Production-grade packages instead of hand-built binaries. Compiling NGINX modules by hand costs hours and breaks on every NGINX update. Our packages are built, tested and signed for your distribution, and they upgrade with the rest of your system.

An NGINX Plus alternative at a fraction of the cost. The GetPageSpeed repository gives you an enterprise-grade NGINX with more than 100 dynamic modules, plus NGINX-MOD, our performance-patched NGINX build.

More than NGINX. Your subscription also covers Varnish and its modules, security software, kernel modules and CLI utilities on RPM systems, and Everpatch security-patched PHP and kernels for end-of-life Linux.

Security as a feature, not an afterthought. See Security and trust below.

Subscribe now

Which Linux distributions are supported?

RPM: RHEL and every RHEL derivative (Rocky Linux, AlmaLinux, Oracle Linux, CentOS, CloudLinux), Amazon Linux and Fedora.

APT: current Debian and Ubuntu LTS releases. The exact list of releases and modules is on the Debian and Ubuntu repository page.

Which architectures are supported?

Both x86_64 (amd64) and aarch64 (arm64), including AWS Graviton.

Prefer to skip the repository setup entirely? NGINX-MOD ships as two AWS Marketplace listings (BETA), one for x86_64 (Intel/AMD) and one for AWS Graviton (arm64), on an Amazon Linux 2023 base.

How do I set up the repository on Debian or Ubuntu?

One package configures the APT source, our signing key and the apt hook:

curl -fsSLO https://extras.getpagespeed.com/release-latest.deb
sudo apt install ./release-latest.deb
sudo apt update

Then install modules as usual, for example sudo apt install nginx-module-brotli. Modules register themselves in /etc/nginx/modules-enabled, so sudo systemctl reload nginx is all it takes. Full guide: NGINX modules APT repository for Debian and Ubuntu.

How do I activate my subscription on a server?

Run this once on the server, on RPM and APT systems alike:

sudo extras activate

The extras command ships with our repository package and confirms, in seconds, that this server is covered.

Security and trust

Signed packages and metadata. Every RPM and DEB package is signed, and so is the repository metadata, so you know you are installing genuine builds. Our official key fingerprints are listed on the GPG keys page.
Security advisories by email. When an NGINX or PHP vulnerability affects the versions your servers run, we let you know when it’s time to upgrade, and a monthly security digest summarises what changed.
Fast security releases. Module packages for new NGINX releases ship within 48 hours.
Extended lifecycle. Everpatch keeps end-of-life systems such as CentOS 7 patched: kernel, base OS and PHP.
SBOMs and build provenance. Ultra subscribers get signed SBOMs and build provenance for compliance and supply-chain audits.

How do I enable repository metadata verification on RPM systems?

By default, yum and dnf only check signatures on the packages themselves. To also verify the repository metadata, run:

sed -i 's@repo_gpgcheck=.*@repo_gpgcheck=1@' /etc/yum.repos.d/getpagespeed-extras.repo

On RHEL 8 and later, dnf config-manager handles wildcards, so this is cleaner:

dnf config-manager --setopt repo_gpgcheck=1 "getpagespeed-*" --save

APT verifies the signed repository metadata on every apt update out of the box.

Are there modules for NGINX mainline?

Yes. On RPM systems, enable the mainline channel before installing modules:

sudo yum -y install yum-utils
sudo yum-config-manager --enable getpagespeed-extras-mainline
sudo yum -y install nginx-module-security

On Debian and Ubuntu:

sudo getpagespeed-extras-channel mainline && sudo apt update

Switching from mainline back to stable NGINX

Mainline gets far more frequent updates than stable. To go back on RPM systems:

sudo yum-config-manager --disable getpagespeed-extras-mainline
sudo yum -y downgrade "nginx*"

On Debian and Ubuntu, run sudo getpagespeed-extras-channel stable, then sudo apt update.

Do I need the nginx.org repository on my system?

No. The GetPageSpeed repository includes both NGINX and its dynamic modules.

I already installed NGINX from nginx.org, EPEL or my distribution. How do I migrate?

Set up our repository, then run sudo dnf upgrade (or sudo apt upgrade on Debian and Ubuntu). Your NGINX configuration stays intact and works with GetPageSpeed packages.

The simplest route is our NGINX-MOD AMI from AWS Marketplace, for x86_64 (Intel/AMD) or AWS Graviton (arm64). You subscribe on AWS Marketplace, and each instance licenses itself from its AWS identity, so it needs no static IP.

Running your own image? For a single EC2 instance, allocate an Elastic IP and use it when signing up. If the address changes, a license token keeps NGINX on that server covered.

Can I use the GetPageSpeed repository in a load-balanced environment on AWS or Azure?

Yes. Route the outbound traffic of your instances through one static public IP and subscribe that IP:

AWS: create a NAT Gateway with an Elastic IP in your VPC, and route your private subnets’ outbound traffic through it.
Azure: create a NAT Gateway in your Virtual Network, attach a static public IP, and route your subnets’ outbound traffic through it.

For organizations with many servers, a Fleet subscription keeps licensing simple.

I have changed my server. How do I associate the new IP?

Change the server IP yourself in the Client Area. The new IP is active within a few minutes, and you can change it again after 24 hours.

I don’t see my NGINX module in your packages

You can submit NGINX modules for continuous builds. Modules are rebuilt with every module and NGINX release, within 24 hours.

RHEL: No package epel-release available

Unlike CentOS, RHEL has no EPEL configuration in its base repositories, so install it before the GetPageSpeed release package:

RHEL=$(rpm -E %{rhel})
sudo yum install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-$RHEL.noarch.rpm
sudo yum-config-manager --enable epel
sudo yum -y install https://extras.getpagespeed.com/release-latest.rpm

Amazon Linux support?

We support all major versions of Amazon Linux. On Amazon Linux 2, run amazon-linux-extras install epel before installing the GetPageSpeed release package.

Control panels and third-party repositories compatibility

The GetPageSpeed repository is fully compatible with the base OS repositories and EPEL, and it is ideal for building your own web stack without a control panel.

Known compatibility issues with control panels:

cPanel is not compatible with NGINX Extras.
cPanel is not compatible with clearmage2 due to limitations in cPanel’s PHP packaging.
DirectAdmin has known compatibility issues and is not compatible with NGINX Extras.
Plesk users have a dedicated build: NGINX Extras for Plesk.

“Cannot open: … Skipping.” when installing the release package

If installing the GetPageSpeed release package prints:

Cannot open: https://extras.getpagespeed.com/release-latest.rpm. Skipping.
Error: Nothing to do

your system clock is wrong, so the SSL certificate cannot be verified. Fix it by enabling NTP synchronization.

What is the difference between CentOS 7 and Amazon Linux 2 NGINX packages?

NGINX for Amazon Linux 2 is built against OpenSSL 1.1.1, so TLS 1.3 works out of the box. On CentOS 7, install NGINX-MOD for TLS 1.3.

Upgrading from NGINX-QUIC to standard NGINX or NGINX-MOD

All our NGINX builds are QUIC-enabled, so the old dedicated NGINX-QUIC packages and channel are obsolete. You can enable HTTP/3 with the standard package. To switch:

Remove the QUIC channel: yum upgrade getpagespeed-extras-release; rm -rf /etc/yum.repos.d/getpagespeed-extras-nginx-quic.repo
Downgrade to stable NGINX: yum downgrade nginx. If that fails, list installed modules with yum list installed | grep nginx, look up the matching versions in the stable channel, and reinstall them by exact version, e.g. yum install nginx-1.26.0 nginx-module-brotli-1.26.0+0.1.4.

Once you’re on stable NGINX again, consider switching to NGINX-MOD.

Still have questions?

We’re here to help. Contact us with any questions about subscriptions, compatibility or getting started.

Ready to enhance your server? Subscribe now and get 100+ NGINX modules, Varnish packages and enterprise-grade security tools for RPM and APT systems.