mod_pagespeed 1.1 · cPanel / EA4

mod_pagespeed for cPanel / EasyApache 4

Actively maintained since 2024. Signed RPMs from We-Amp, served out of packages.modpagespeed.com. Drops into EasyApache 4 as ea-apache24-mod_pagespeed — same package name Google's archived apache/incubator-pagespeed-cpanel repo used before it was archived in 2023. We picked up the upstream and kept shipping; the SRPM in this repo is the canonical EA4 build today.

Install

EasyApache 4 ships only on RHEL-family hosts. Write the yum repo file, then dnf install the module:

1. Write the yum repo file

On EL9 hosts (AlmaLinux 9, Rocky 9, RHEL 9):

sudo tee /etc/yum.repos.d/modpagespeed-ea4.repo >/dev/null <<'EOF'
[ea4]
name=mod_pagespeed for EasyApache 4
baseurl=https://packages.modpagespeed.com/yum/ea4/el9/x86_64/
enabled=0
gpgcheck=1
gpgkey=https://packages.modpagespeed.com/pubkey.gpg
EOF

On EL8 hosts (AlmaLinux 8, Rocky 8, RHEL 8) — replace el9 with el8 in the baseurl:

sudo tee /etc/yum.repos.d/modpagespeed-ea4.repo >/dev/null <<'EOF'
[ea4]
name=mod_pagespeed for EasyApache 4
baseurl=https://packages.modpagespeed.com/yum/ea4/el8/x86_64/
enabled=0
gpgcheck=1
gpgkey=https://packages.modpagespeed.com/pubkey.gpg
EOF

2. Install the module

sudo dnf install --enablerepo=ea4 ea-apache24-mod_pagespeed

enabled=0 + --enablerepo=ea4 keeps the EA4 RPM tree out of routine dnf update runs unless you ask for it. The package is signed with key rsa4096/F50D6054F10712A0 — same key as the rest of packages.modpagespeed.com.

A one-liner installer that writes the EA4 stanza for you is on the backlog. Today the operator authors modpagespeed-ea4.repo by hand; the existing install.sh targets the stock apt + yum trees only.

After install — WHM Customize UI

The RPM drops a module file but does not flip it on. Apache only loads mod_pagespeed after the operator ticks the box in WHM and rebuilds.

WHM → Software → EasyApache 4 → Customize on the current profile.
Open the Apache Modules step. mod_pagespeed appears alongside the other EA4 modules.
Tick the checkbox. Review, then Provision. EA4 rebuilds Apache.
When the provision finishes, the module is loaded and the filter runs on every vhost served by ea-apache24-httpd.

Prefer the command line? On a fresh provision the module is also wired into /etc/apache2/conf.d/modpagespeed.conf. Edit that file (or a per-vhost include) the same way you would on any RHEL Apache host — see the getting-started guide for the directive reference.

Activate a license

The trial and activation flow runs from the global admin console on the server. Same path on every server mod_pagespeed 1.1 supports — Apache, nginx, IIS, Envoy:

https://your-host.example.com/pagespeed_global_admin

Open /pagespeed_global_admin on any vhost. The admin route is global to the server, not scoped to one vhost; /pagespeed_admin/ is the per-vhost statistics endpoint and does not run the trial flow.
Click Start trial. The console hands off to FastSpring checkout, which collects a card. The trial token mints on return.
After 14 days the card is charged. Cancel from the console before day 15 and you pay nothing. The same screen accepts an existing license key if you already own one.

Without a valid token the worker stops optimizing and Apache passes requests through to the origin unmodified. The console itself stays reachable so you can re-enter or renew a token at any time.

Operational warning

Remove before `cpanel/elevate`. Reinstall after.

Any third-party EA4 module — ea-apache24-mod_pagespeed included — blocks cpanel/elevate on EL8 → EL9 and EL9 → EL10 OS upgrades. This is the same precedent mod_passenger sets. cPanel's preflight stops on the package; the upgrade does not start.

Three-step runbook on the OS upgrade window:

sudo dnf remove ea-apache24-mod_pagespeed — the module unwires and Apache rebuilds without it. The license token and any /etc/apache2/conf.d/modpagespeed.conf stay on disk.
Run /scripts/elevate-cpanel through the OS upgrade. EA4 itself migrates to the new EL release.
Re-enable the yum repo for the new EL release (baseurl=…/yum/ea4/elNN/x86_64/) and reinstall the module: sudo dnf install --enablerepo=ea4 ea-apache24-mod_pagespeed. The existing config and token are picked up unchanged.

The post-install script also writes a one-line reminder to /etc/motd so it surfaces at the next SSH session before the upgrade window.

Pricing

Same as every other mod_pagespeed 1.1 install path: $49/server/month, or $39/server/month billed annually ($588/server/year). One license per Apache instance. No per-request fees. No EA4-specific SKU.

First 14 days are free. The trial collects a card at checkout via FastSpring; cancel from /pagespeed_global_admin before day 15 and you pay nothing.

See full pricing

Not yet supported

Honest about the edges of the channel:

• EL10. Waiting on EA4 itself to ship EL10. We'll add the el10 tree to the repo once ea-apache24-httpd publishes there.
• arm64. EA4 RPMs ship x86_64 only at launch. arm64 is on the backlog; contact us if it blocks you.
• Ubuntu EA4. cPanel's Ubuntu EA4 support is partial / preview. We ship RHEL-family only initially — AlmaLinux 9, Rocky 9, and RHEL 9.
• WHM plugin UI. Config still lives in modpagespeed.conf and per-vhost includes. A WHM plugin for point-and-click config is a question we revisit once the install base passes ~50 servers.

The module is built against EA4's Apache ABI (Module Magic Number 20120211), which cPanel has held stable across the entire Apache 2.4 series. Routine ea-apache24 updates keep the same MMN, so a yum update does not disturb the installed module. If a future Apache release ever changes the ABI, the package's ea-apache24-mmn requirement makes yum update hold the Apache upgrade with a clear dependency message instead of loading an incompatible module, so your site keeps serving. We track every ea-apache24 release and publish a matching signed rebuild when an ABI change requires one.

Maintained upstream. Signed RPMs. cPanel-native install.

Card required at checkout — cancel before day 15 and pay nothing.

Back to install Email the maintainer