RPM Repository FAQ

You will likely find an answer to your question here.

It’s simple. The GetPageSpeed repository saves you both time and money.
Instead of having to compile software manually, doing it wrong, and spending much labor in the process – use our production-grade packages.

Our NGINX/Varnish packages are built with high performance and security in mind.

Ever heard of NGINX-Plus? We’re better.

The GetPageSpeed repository is your way to the enterprise NGINX build with 50+ modules so you can set up the top-notch high-performance web server in minutes.

If you are serious to run your websites in production, you will appreciate the nearly free subscription price (compared to $2.5k+ NGINX-Plus).

GetPageSpeed provides far more than NGINX module packages alone, for a funny subscription price.
With the GetPageSpeed repository you can literally extend your CentOS/RHEL system with pretty much everything that you need for a fast and secure server setup:

Varnish and its modules
Security packages
Desktop OS packages
Kernel modules
CLI utilities

All of that is available once you subscribe. We don’t abandon a single package. Everything is consistent, up-to-date, stable, and production-ready.

Subscribe now

What is NGINX-Plus anyway? And why do you say GetPageSpeed is better?

NGINX-Plus is a feature-rich build of NGINX and its modules which come as a package repository.
The GetPageSpeed repository is a better NGINX-Plus alternative because it costs a lot less and provides more features.

Are there modules for the NGINX mainline?

Of course. Make sure you have the extra repo enabled before installing them:

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

Then install modules as usual, e.g.:

sudo yum -y install nginx-module-security

Switching from mainline to stable NGINX branch

The mainline branch of NGINX has far more frequent updates than the stable one.
For this or other reasons, you may want to downgrade to the stable branch.

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

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

No. You do not need to have the RPM repository from nginx.org/packages.
The GetPageSpeed repository includes both NGINX and dynamic modules for it.

If you had nginx from nginx.org, you don’t have to uninstall it or do anything special about it.

If you want to benefit from SELinux fixes (e.g. 1) available in the nginx package by GetPageSpeed, simply reinstall it.
This would replace the package you had from nginx.org with ours. No configuration will be lost:

yum reinstall nginx

I have already installed NGINX from the EPEL repository. How to migrate?

Simply run yum upgrade once the subscription is activated. All of your NGINX configurations stay intact and work fine with GetPageSpeed-supplied packages.

Simply allocate an Elastic IP and specify it while signing up here.

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

If more than 3 months passed since your subscription has been set up initially, you can bind it to the new server’s IP address using a simple API call. On the new server, run:

curl 'https://www.getpagespeed.com/new-server-hello.php?subscr_id=XXXXXX'

Replace XXXXXX with your subscription ID (e.g. from PayPal).

Likewise, you can change the associated IP later again if at least 3 months have passed from the prior IP change.

If you want to change IP earlier than 3 months minimum, cancel your current subscription and set up a new one.

I don’t see my NGINX module in your packages

You can submit NGINX modules for continuous build in our system here.
The modules are rebuilt with every module and NGINX release, within 24 hrs.

Metadata GPG verification?

Our repository signs both RPM packages and repository metadata with our GPG signature. So you know you’re getting genuine builds.

By default, yum will only check signatures on packages themselves. You can also instruct it to check the signature of the repository’s metadata. To do this, run:

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

Worth noting that in RHEL 8+, dnf config-manager grew smart enough to handle wildcards so it’s cleaner to use:

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

Oracle Linux, AlmaLinux, and Rocky Linux are supported?

Yes, all RHEL derivative operating systems like Oracle Linux, AlmaLinux, and Rocky Linux are fully supported by the GetPageSpeed RPM repository.

RHEL: No package epel-release available

RHEL (unlike CentOS), does not have the required EPEL repository configuration in the base repositories. So it must be installed prior to installing the GetPageSpeed release package, as such:

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 2 support?

It is a supported OS. Prior to installing the GetPageSpeed release package, run:

amazon-linux-extras install epel

Control panels and third-party repositories compatibility

In general, the GetPageSpeed repository has perfect compatibility with the base OS repositories, as well as the EPEL repository.
The GetPageSpeed repository is likewise perfect for building your own web stack without a control panel.

Beware of the following known compatibility issues with control panels:

cPanel is not compatible with NGINX Extras
cPanel is not compatible with clearmage2 due to not providing PHP capability in their PHP packages (ridiculous packaging from cPanel)
DirectAdmin is very much disgusting, and not compatible with NGINX extras

I am a non-profit organization that needs things for free

You may want to read about the free RPM repository usage.
Note that only a limited set of packages is available free of charge. NGINX module pacakges are not free.

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

When running installation of the GetPageSpeed release package, you might get these errors:

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

This only means that your system’s clock is incorrect. It must be well synchronized and have a proper time set, in order to verify the SSL certificate.
Fix your system by enabling NTP synchronization.

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

The NGINX packages for Amazon Linux 2 are built against OpenSSL 1.1.1, thus TLS 1.3 is supported out of the box.

NGINX on CentOS 7 can support TLS 1.3 as well by installing the NGINX-MOD package.

If you have another question, we are happy to receive your email and assist.