Set up Pagereckon on cPanel hosting
On cPanel hosting, Apache writes one access log per domain, and Pagereckon reads that file to count visitors and bots. This guide shows where the file lives, how to check that PHP can open it, and what to pick in the Find my log wizard.
Most cPanel accounts need no shell work at all. You install the plugin, open Settings, and press one button.
Where cPanel keeps the access log
cPanel calls these files domain logs, or domlogs. Each domain on the account gets its own file, named after the domain. When the site runs on HTTPS, a second file holds the secure traffic, with -ssl_log at the end of the name. Since almost every WordPress site runs on HTTPS today, the -ssl_log file is usually the one you want.
| Path | What it is |
|---|---|
| `~/access-logs/example.com-ssl_log` | Link in your home folder to the live HTTPS log |
| `~/access-logs/example.com` | Live log for plain HTTP requests |
| `/etc/apache2/logs/domlogs/user/` | Real folder on current cPanel servers |
| `/usr/local/apache/domlogs/example.com` | Older layout, still present on some servers |
| `~/logs/` | Archived copies as .gz files (Raw Access archive) |
The access-logs folder in your home directory is a link that cPanel creates for you. It points to the real domlogs folder, which sits outside your home. So a PHP process that runs as your cPanel user can often read the log through that link.
Pick the log in the Find my log wizard
First, install the free plugin from the download page and activate it. Then open Pagereckon, Settings. The Find my log table lists every file PHP can read in the usual cPanel places, such as /usr/local/apache/domlogs/, /etc/apache2/logs/domlogs/ and ~/access-logs/.
- Look for the row with your domain and a check mark under This site.
- Check the Format column. On cPanel it should say combined.
- Press Use this log. Pagereckon reads the file from the top on its next run.
For each file, the wizard reads a short sample of lines, finds the format and checks whether the lines belong to your site. It also shows one sample line with the IP hidden. If no row appears, paste the path into the Test a path field instead. For example, try /home/user/access-logs/example.com-ssl_log with your own user name and domain.
When cPanel blocks PHP from the log
Sometimes the wizard finds nothing, or the test says the file exists but PHP cannot read it. There are two usual causes on cPanel servers.
File permissions on the cPanel server
The domlogs folder often belongs to root and a log group. If your PHP user is not in that group, the file stays closed to WordPress. In that case, ask your host a short question: can the PHP user of my account get read access to my domain log? Many hosts say yes, because the log already belongs to your account.
open_basedir limits
Some cPanel hosts set open_basedir so PHP can only open files inside your home folder. The test then reports that PHP may not look there. Since ~/access-logs sits inside your home, try that path first. If it still fails, ask the host to add the domlogs path to open_basedir.
Log rotation and archived .gz files
cPanel processes the logs for its own statistics about once a day. On the Raw Access page you can also tell it to archive the logs in your home folder and to remove last month's archive at the end of each month. Those archives land in ~/logs as compressed .gz files.
Pagereckon handles this on its own. It reads new lines every 10 minutes, so it sees each line long before cPanel moves it. When a file shrinks or starts over, Pagereckon notices and reads it again from the top. In addition, you can add an older .gz archive to the path list to import past days. Pagereckon reads each .gz file once.
Run the cPanel cron job for faster updates
By default, WordPress cron processes the log every 10 minutes, but only when someone visits the site. A real server cron is steadier and lighter. In cPanel, open Cron Jobs, choose every 5 minutes, and enter this command with your own path:
*/5 * * * * wp --path=/home/user/public_html pagereckon ingest --max-seconds=240If the cron cannot find wp, use the full path to WP-CLI on your server. The Settings page prints the exact line for your site, so you can copy it from there.
Fallback: the PHP request log
Some shared hosts never let PHP read the access log. When that happens, switch Where the visits come from to the PHP request log. Pagereckon then writes its own log of every request that reaches WordPress.
However, this mode is less complete. Pages served from a page cache, such as LiteSpeed Cache or WP Rocket, never reach PHP, so those views and the bots that get them are missing. As a result, your numbers will be lower than with the real cPanel log. The server log stays the better choice whenever you can get it. To see how Pagereckon then sorts people from bots, read the WordPress statistics plugin overview or the privacy notes.
cPanel questions
Which cPanel log should I pick, the plain one or -ssl_log?
Pick the -ssl_log file when your site runs on HTTPS. The plain file only holds HTTP requests, which are mostly redirects on a modern site.
Does Pagereckon need root access on cPanel?
No. It only needs read access to your own domain log. On many cPanel accounts the access-logs link in your home folder already gives that.
Can I import old cPanel logs?
Yes. Add the archived .gz files from ~/logs to the path list. Pagereckon reads each one once and keeps your retention setting, 90 days by default.
Do I need a cookie banner for this?
Pagereckon sets no cookies and keeps no visitor IP addresses in its database. It reads a log your host keeps anyway. Check your own legal situation, but there is nothing to consent to.