Emergency server help: get in touch

GoAccess cPanel: AWStats and Webalizer Replacement Before 142

cPanel deprecates AWStats, Webalizer and Analog in version 140, plans to remove them in version 142, and says GoAccess support will be added before they are removed. This guide explains what changes, how to install and test GoAccess now on 136 and 138, and how to prepare customers who depend on the old reports.

Published Updated 8 min read

AWStats, Webalizer and Analog have shipped with cPanel for two decades, and cPanel’s deprecation plan marks all three as deprecated in version 140 and removed in version 142, and says GoAccess support will be added before they are removed. Webalizer stopped receiving upstream updates years ago, AWStats needs Perl CGI and a sizeable daily processing job, and none of them understand modern log formats well. GoAccess is a fast C-based analyser that produces an interactive HTML report from the same domlogs, in a fraction of the time. If you run 136 or 138 today, you can install GoAccess cPanel reports now, run them in parallel, and remove the dependency on the old tools before the update forces the issue.

Short answer: Install GoAccess from EPEL with dnf install epel-release goaccess, run it against /etc/apache2/logs/domlogs/<domain> with --log-format=COMBINED and let GoAccess write the HTML report as each account (runuser) into that account’s private ~/tmp/goaccess/, then schedule that for every account from /etc/cron.daily before cpanellogd truncates the logs. Once the reports match AWStats for a day, disable AWStats and Webalizer in WHM » Statistics Software Configuration so the removal planned for version 142 changes nothing. (Reviewed October 2026.)

Update, 9 October 2026: the report commands now run GoAccess as the account instead of as root, so a link planted in a customer’s home cannot redirect a root write (tested on our cPanel lab server: a planted link to a root-owned file was refused, the old recipe overwrote it), and reports stay private. Also corrected to cPanel’s deprecation plan: AWStats, Webalizer and Analog Stats are deprecated in version 140 and due for removal in version 142. Update, 8 October 2026: cPanel’s notice to licence holders says GoAccess now replaces AWStats as cPanel’s web statistics tool. Check WHM » Statistics Software Configuration on your build to see which report generators are still enabled before you rely on the timeline below.

What is actually changing

cPanel deprecates the three legacy analysers in version 140 and plans to remove them from the distribution in version 142. The Metrics section in cPanel loses the AWStats, Webalizer and Analog icons; bandwidth accounting is not affected because it is done by cpanellogd independently of the report generators. Existing report data in ~/tmp/awstats and ~/tmp/webalizer is not deleted by the update, but nothing will regenerate it. Check the release notes for your build to see whether GoAccess is already exposed in the cPanel interface, because cPanel has only committed to adding GoAccess support before the old analysers are removed.

If your servers are on LTS 134 they will not see this until they move to a later LTS, but customers who move between your servers will notice differences, so it is worth standardising early.

Install GoAccess on the server

GoAccess is packaged in EPEL for AlmaLinux 8, 9 and 10, and in the Ubuntu 22.04 and 24.04 archives. On AlmaLinux:

dnf install epel-release -y
dnf install goaccess -y
goaccess --version

The EPEL build is usually a version or two behind upstream but supports real-time HTML output and GeoIP if you add a database. On Ubuntu use apt install goaccess. Once cPanel ships its own ea-goaccess or equivalent package, prefer that over EPEL so the two do not conflict; check rpm -qa | grep -i goaccess after each major update from 140 onwards.

Generate a report for one domain

cPanel’s domlogs are in Apache combined format with a small twist: the vhost files under /etc/apache2/logs/domlogs/ do not include the vhost name, so use the COMBINED preset:

D=example.com; U=USER
runuser -u "$U" -- mkdir -p -m 700 "/home/$U/tmp/goaccess"
cat "/etc/apache2/logs/domlogs/$D" \
  | runuser -u "$U" -- sh -c 'umask 077; exec goaccess --log-format=COMBINED -o "$1" -' sh "/home/$U/tmp/goaccess/$D.html"

For the SSL log, the file is example.com-ssl_log in the same directory. To combine both:

cat "/etc/apache2/logs/domlogs/$D" "/etc/apache2/logs/domlogs/$D-ssl_log" \
  | runuser -u "$U" -- sh -c 'umask 077; exec goaccess --log-format=COMBINED -o "$1" -' sh "/home/$U/tmp/goaccess/$D.html"

Two things matter here. First, root only reads the log; GoAccess itself runs as the account (runuser -u USER) and writes the report. The account owns its home directory, so if root wrote there directly, a symbolic link planted at the report path could make root overwrite any file on the server. Run as the account, a planted link can only reach files the account could already change. Second, keep the report private: a stats page reveals URLs, referrers and visitors’ IP addresses. ~/tmp/goaccess/ is not served by the web server and umask 077 makes the file readable only by the account. Customers can download it from File Manager; if you publish it on the web, put it in a directory protected with cPanel’s Directory Privacy, and copy it there as the account, never as root.

Run it for every account on a schedule

Until the native integration lands, a cron job is the practical approach. This script walks every account and its domains. Root reads each domain’s logs, and GoAccess runs as the account to write one private report per domain into ~/tmp/goaccess/, so there is nothing to chown afterwards:

#!/bin/bash
# Daily GoAccess reports for every cPanel account.
# Root only reads the logs. Each report is written by goaccess running as the account
# (runuser), so a link planted in the account's home cannot redirect a root-owned write.
set -u -o pipefail
fail=0
for userfile in /var/cpanel/users/*; do
  user=${userfile##*/}
  id "$user" >/dev/null 2>&1 || continue
  home=$(getent passwd "$user" | cut -d: -f6)
  [ -d "$home" ] || continue
  runuser -u "$user" -- mkdir -p -m 700 "$home/tmp/goaccess" || continue
  runuser -u "$user" -- chmod 700 "$home/tmp/goaccess"
  while read -r dom; do
    case "$dom" in ''|*[!a-z0-9.-]*) continue ;; esac
    logs=()
    for f in "/etc/apache2/logs/domlogs/$dom" "/etc/apache2/logs/domlogs/$dom-ssl_log"; do
      [ -f "$f" ] && logs+=("$f")
    done
    [ "${#logs[@]}" -gt 0 ] || continue
    # "$1" is the report path, passed as the first argument after "sh". Errors go to stderr (cron mail).
    if ! cat "${logs[@]}" | runuser -u "$user" -- sh -c 'umask 077; exec goaccess --log-format=COMBINED --no-progress -o "$1" -' sh "$home/tmp/goaccess/$dom.html" >/dev/null; then
      echo "goaccess failed for $user / $dom" >&2
      fail=1
    fi
  done < <(grep -E '^DNS[0-9]*=' "$userfile" | cut -d= -f2)
done
exit "$fail"

The script exits with status 1 and names the account and domain if any report fails, so cron mails you the failure instead of hiding it. Run it from /etc/cron.daily before cpanellogd’s processing hour, because if you have “delete access logs after stats” enabled the domlogs are truncated afterwards. GoAccess only sees what is in the file when it runs; for historical reports, feed it the gzipped archives from ~/logs/ as well using zcat.

A common pitfall is CageFS on CloudLinux: if you later let users run GoAccess themselves, add it to the CageFS skeleton with cagefsctl --addrpm goaccess and update the cage.

Prepare customers

Most customers use the stats icons rarely, but the ones who do (agencies reporting to their own clients, for example) will notice. Before your servers move to 142:

  • Send a notice explaining that AWStats and Webalizer are being retired by the vendor and pointing to the new report location.
  • Export the AWStats history for anyone who asks: the monthly data files in ~/tmp/awstats/awstats*.txt are plain text and can be archived.
  • Offer a hosted analytics alternative (Matomo, Plausible or a similar self-hosted tool) for customers who want long-term trends, since GoAccess is a log analyser and does not keep a database across runs unless you use its persistence options.

Verify

Open a generated report in a browser and confirm the visitor count roughly matches what AWStats reported for the same day; small differences are expected because the two tools count bots differently. Check ls -la /home/*/tmp/goaccess/ after the first cron run to confirm ownership and that every active domain has a file. Time the run with time /etc/cron.daily/goaccess-reports and compare it with the AWStats processing time in /usr/local/cpanel/logs/cpanellogd.log; on most servers GoAccess finishes in under a tenth of the time. Once you are satisfied, disable AWStats and Webalizer under WHM » Statistics Software Configuration so the daily run stops doing redundant work, and the version 142 removal becomes a non-event.

Official documentation: cPanel & WHM documentation, Linux man pages.

Related guides: “cPanel license is invalid”: troubleshooting manage2, IP changes and firewalls · cPanel 2026 pricing and licensing explained: Solo, Admin, Pro, Premier and WP Squared · Account quotas show “unlimited”: fixquotas and XFS/ext4 quota repair on cPanel.

Frequently asked questions

Does removing AWStats and Webalizer affect bandwidth usage in cPanel?

No. Bandwidth accounting is done by cpanellogd independently of the report generators, so account bandwidth graphs, quotas and overage notices continue to work after the analysers are gone.

Can customers still see their old AWStats history after cPanel removes it in 142?

The data files under ~/tmp/awstats/ are not deleted by the update, but nothing regenerates them and the viewer icon disappears. Export the monthly awstats*.txt files for customers who need the history before the server moves to 142.

Is GoAccess free to use on a cPanel server?

Yes. GoAccess is open source and packaged in EPEL and the Ubuntu archives, and cPanel’s deprecation plan says it will add GoAccess support before the old analysers are removed.

Share this guide

Free website test

Is your website set up right?

Check SSL, security headers, redirects, robots.txt, sitemap, llms.txt and security.txt in one test. It takes about 30 seconds.