-
-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Statistics not showing #1185
Comments
Hi @Saffronbunny, it looks like something changed with your server configuration that affects the PHP CLI setup. Specifically, when loading WordPress through PHP CLI (which is done by default when archiving reports), there appears to be an failure in loading redis, causing a failure. (The specific error message is in the system report as Resolving the error with redis should solve the problem (you may need to contact your hosting provider to fix this unless you are able to change the server configuration yourself). Alternatively, you can try enabling archiving via HTTP requests in |
Hi! Thanks!
|
No, this shouldn't affect the error you're seeing.
It depends a bit on your infrastructure/server config, but 50k pageviews per month is a good upper limit.
Yes, just the last setting in that image. |
OK, I can see it's registering now. One more question - how can I filter out my own visits to the site? |
@Saffronbunny you can exclude your own visits using the settings in the |
I don't have any visitors registered in the last few months. I can only see there are visitors registered in the last 24 hours in real time and visitors logg, but apparently they aren't archived.
Archiving ran successfully the last time: 12 june 2024 13:07:14.
I include the errors an reports I find.
Matomo Cron Error
An error occurred during Matomo archiving. See error details in the Diagnostics page.
DIAGNOSTICS
Matomo Archive Warnings: 'Got invalid response from API request: ?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=day&date=2024-08-14&format=json&trigger=archivephp. Response was '
Matomo system report.txt
The text was updated successfully, but these errors were encountered: