Skip to content
Docs / Install

Set up Pagereckon on a Plesk server

Plesk keeps a set of access logs for every domain, and Pagereckon reads one of them to count visitors, bots and AI crawlers. This guide shows where those files live, which one to choose, and what to do when PHP cannot open it.

On most Plesk servers the setup takes a few minutes. You only need the file path and read access.

The Pagereckon team Updated
Plesk at a glance, from Pagereckon

Where Plesk keeps the access logs

The panel stores domain logs in a system folder and shows them again in the domain's own folder. Both names point to the same files, because of hard links. So you can use either path.

Access log paths on Linux (replace example.com)
PathWhat it holds
`/var/www/vhosts/system/example.com/logs/`The real folder Plesk writes to
`/var/www/vhosts/example.com/logs/`Same files, inside the subscription folder
`access_ssl_log`Apache log for HTTPS requests
`access_log`Apache log for plain HTTP requests
`proxy_access_ssl_log`nginx log for HTTPS requests
`proxy_access_log`nginx log for plain HTTP requests

You can also see these files under Websites and Domains, Logs, which lists the Apache and nginx access logs by default.

Apache log or nginx log on Plesk?

By default, the Linux version runs nginx in front of Apache. Apache builds the dynamic pages, while nginx serves static files such as images, CSS and scripts on its own. The panel calls this smart static files processing.

That matters for Pagereckon. Each real browser loads a tiny beacon image once per session, and Pagereckon uses it to tell people from bots. On a default setup, nginx answers that image request itself, so it never shows up in the Apache log. As a result, the nginx file proxy_access_ssl_log usually gives the most complete picture, because nginx sees every request first.

  • Use proxy_access_ssl_log when proxy mode is on, which is the default.
  • Use access_ssl_log only when nginx is off for the domain.
  • Do not list both files, or every page view counts twice.

Pick the Plesk log in Find my log

First, download the free plugin, install it and activate it. Then open Pagereckon, Settings. The Find my log table lists the files PHP can read in the usual folders, with the format and a check mark when the lines belong to your site.

Next, check which file the table offers. The wizard looks for the Apache files, access_ssl_log and access_log, in both folders. If you want the nginx file instead, paste its path into Test a path, for example /var/www/vhosts/example.com/logs/proxy_access_ssl_log. The test reads a short sample of lines and tells you the format. When it says combined, enter the same path in Access log path(s) and save.

When PHP cannot read the Plesk log

The panel usually runs PHP as the system user of the subscription. That user may not have read access to the log folder. In that case the test says the file exists, but PHP cannot read it. Ask your host or server admin to give that user read access to the domain's logs.

open_basedir in Plesk PHP settings

You can see open_basedir per domain under PHP Settings. If the test reports that PHP may not look there, use the path inside the subscription, /var/www/vhosts/example.com/logs/, rather than the system folder. If that still fails, the admin can add the logs folder to open_basedir.

Log rotation in Plesk

The panel can rotate, compress and delete old domain logs. You find the options under Logs, Log Rotation. Rotation does not break Pagereckon. It reads new lines every 10 minutes, and when a file starts over, it reads it again from the top.

In addition, you can import older days. Add a rotated .gz copy to the path list, or use a pattern such as /var/www/vhosts/example.com/logs/proxy_access_ssl_log*. Pagereckon reads each .gz file once.

Server cron for Plesk

WordPress cron processes the log every 10 minutes when the site gets visits. A real cron job is steadier. Open Scheduled Tasks, add a command, and run it every 5 minutes:

Scheduled task
*/5 * * * * wp --path=/var/www/vhosts/example.com/httpdocs pagereckon ingest --max-seconds=240

The Settings page in Pagereckon prints this line with your own path, so you can copy it.

If the host hides the log

Some managed plans do not let PHP read any log. Then switch Where the visits come from to the PHP request log. Pagereckon writes its own daily log of the requests that reach WordPress.

However, this fallback is less complete. Pages served from a page cache never reach PHP, so those views and the bots that get them are missing, and your numbers will be lower. For the reasons behind a log based count, see the Google Analytics alternative page and the privacy notes.

Plesk questions

Which Plesk log should Pagereckon read?

On a default Plesk setup with nginx in front of Apache, pick proxy_access_ssl_log. It holds every request, including the static files nginx serves itself.

Why does the Plesk log appear in two folders?

The panel writes the files in /var/www/vhosts/system/ and links them into the domain's own logs folder. Both paths open the same file.

Do I need SSH access?

No. The wizard and the Test a path field work from WordPress. You only need SSH or your host if PHP cannot read the file.

Sources and references

Free plugin, optional Pro

See your own AI traffic in ten minutes

Install the free plugin, point it at your access log and read today's humans, bots and AI visits. Then add Pro when you want Search Console and the before and after reports.