Matomo not running #1349
Description
After debug Troubleshooting> Arhive reports
Matomo Archive Warnings: 'Got invalid response from API request: ?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=year&date=2026-01-01&format=json&trigger=archivephp. Response was \'Got invalid response from API request: https://www.bayerisches-bier.de/wp-content/plugins/matomo/app/?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=year&date=2026-01-01&format=json&trigger=archivephp&. The response was empty. This usually means a server error. This solution to this error is generally to increase the value of \'memory_limit\' in your php.ini file. Please check your Web server Error Log file for more details.\''
'Error unserializing the following response from ?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=year&date=2026-01-01&format=json&trigger=archivephp: \'Got invalid response from API request: https://www.bayerisches-bier.de/wp-content/plugins/matomo/app/?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=year&date=2026-01-01&format=json&trigger=archivephp&. The response was empty. This usually means a server error. This solution to this error is generally to increase the value of \'memory_limit\' in your php.ini file. Please check your Web server Error Log file for more details.\''
'2 total errors during this script execution, please investigate and try and fix these errors.'
'2 total errors during this script execution, please investigate and try and fix these errors.'
[26-Jan-2026 14:12:41 UTC] Matomo: Scheduled tasks archive data
[26-Jan-2026 14:12:42 UTC] Matomo: Got invalid response from API request: ?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=year&date=2026-01-01&format=json&trigger=archivephp. Response was 'Got invalid response from API request: https://www.bayerisches-bier.de/wp-content/plugins/matomo/app/?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=year&date=2026-01-01&format=json&trigger=archivephp&. The response was empty. This usually means a server error. This solution to this error is generally to increase the value of 'memory_limit' in your php.ini file. Please check your Web server Error Log file for more details.'
[26-Jan-2026 14:12:42 UTC] Matomo: Error unserializing the following response from ?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=year&date=2026-01-01&format=json&trigger=archivephp: 'Got invalid response from API request: https://www.bayerisches-bier.de/wp-content/plugins/matomo/app/?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=year&date=2026-01-01&format=json&trigger=archivephp&. The response was empty. This usually means a server error. This solution to this error is generally to increase the value of 'memory_limit' in your php.ini file. Please check your Web server Error Log file for more details.'
[26-Jan-2026 14:12:42 UTC] Matomo: 2 total errors during this script execution, please investigate and try and fix these errors.
[26-Jan-2026 14:12:42 UTC] Matomo: Matomo error - An error occurred during Matomo archiving. Details: 2 total errors during this script execution, please investigate and try and fix these errors. => CronArchive.php:546; CronArchive.php:541; CronArchive.php:252; Access.php:558; CronArchive.php:256; ScheduledTasks.php:392; SystemReport.php:160; SystemReport.php:352; class-wp-hook.php:324; class-wp-hook.php:348; plugin.php:517; admin.php:259;
[26-Jan-2026 14:12:42 UTC] Matomo: Matomo error: 'Got invalid response from API request: ?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=year&date=2026-01-01&format=json&trigger=archivephp. Response was \'Got invalid response from API request: https://www.bayerisches-bier.de/wp-content/plugins/matomo/app/?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=year&date=2026-01-01&format=json&trigger=archivephp&. The response was empty. This usually means a server error. This solution to this error is generally to increase the value of \'memory_limit\' in your php.ini file. Please check your Web server Error Log file for more details.\'' 'Error unserializing the following response from ?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=year&date=2026-01-01&format=json&trigger=archivephp: \'Got invalid response from API request: https://www.bayerisches-bier.de/wp-content/plugins/matomo/app/?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=year&date=2026-01-01&format=json&trigger=archivephp&. The response was empty. This usually means a server error. This solution to this error is generally to increase the value of \'memory_limit\' in your php.ini file. Please check your Web server Error Log file for more details.\'' '2 total errors during this script execution, please investigate and try and fix these errors.' => ScheduledTasks.php:406; SystemReport.php:160; SystemReport.php:352; class-wp-hook.php:324; class-wp-hook.php:348; plugin.php:517; admin.php:259;
[26-Jan-2026 14:12:42 UTC] Matomo: ERROR: Uncaught exception: Unable to authenticate with the provided token. It is either invalid or expired. /www/live/bayerisches-bier/htdocs/wp-content/plugins/matomo/app/plugins/Login/Login.php:133
# Errors
* Error Last Successful Archiving Completion: error (Archiving has not yet run successfully )
# Matomo
* Matomo Plugin Version: 5.6.1
* Config exists and is writable.: Yes ("$WP_CONTENT_DIR//uploads/sites/2/matomo/config/config.ini.php" )
* JS Tracker exists and is writable.: Yes ("$WP_CONTENT_DIR//uploads/sites/2/matomo/matomo.js" )
* Plugin directories: Yes ([{"pluginsPathAbsolute":"\/www\/htdocs\/w019cc25\/live\/bayerisches-bier\/htdocs\/wp-content\/plugins\/matomo\/plugins","webrootDirRelativeToMatomo":"..\/plugins"}])
* Tmp directory writable: Yes ($WP_CONTENT_DIR//uploads/sites/2/matomo/tmp)
* Matomo Version: 5.6.2
* Matomo Blog idSite: 1
* Matomo Install Version: 5.6.1 (Install date: 2026-01-26 14:37:01)
* Upgrades outstanding: No
* Upgrade in progress: No
* Current Matomo User Language: en
* Current Matomo Language Cookie Value: None
## Endpoints
* Matomo JavaScript Tracker URL: (https://www.bayerisches-bier.de/wp-content/uploads/sites/2/matomo/matomo.js)
* Matomo JavaScript Tracker - WP Rest API: ($site_url/wp-json/matomo/v1/hit/)
* Matomo HTTP Tracking API: (https://www.bayerisches-bier.de/wp-content/plugins/matomo/app/matomo.php)
* Matomo HTTP Tracking API - WP Rest API: ($site_url/wp-json/matomo/v1/hit/)
## Crons
* Server time: 2026-01-26 13:44:31
* Blog time: 2026-01-26 14:44:31 (Below dates are shown in blog timezone)
* Sync users & sites: Next run: 2026-01-27 14:39:10 (23 hours 54 min) ( Last started: 2026-01-26 14:39:12 (-5 min 19s). Last ended: 2026-01-26 14:39:12 (-5 min 19s). Interval: daily)
* Archive: Next run: 2026-01-26 15:37:04 (52 min 33s) ( Last started: 2026-01-26 14:37:05 (-7 min 26s). Last ended: 2026-01-26 14:37:07 (-7 min 24s). Interval: hourly)
* Update GeoIP DB: Next run: 2026-02-25 14:39:10 (29 days 23 hours) ( Last started: 2026-01-26 14:39:12 (-5 min 19s). Last ended: 2026-01-26 14:39:12 (-5 min 19s). Interval: matomo_monthly)
## Mandatory checks
* PHP version >= 7.2.5: ok
* PDO extension: ok
* PDO\MYSQL extension: ok
* MYSQLI extension: ok
* Other required extensions: ok
* Required functions: ok
* Required PHP configuration (php.ini): ok
* Directories with write access: ok
## Optional checks
* 64-bit PHP Binary: ok
* Tracker status: ok
* Memory limit: ok
* Time zone: ok
* Open URL: ok
* GD > 2.x + FreeType (graphics): ok
* Other extensions: ok
* Other functions: ok
* Filesystem: ok
* Error Last Successful Archiving Completion: error (Archiving has not yet run successfully )
* Database abilities: ok
* Max Packet Size: ok
* Warning Geolocation: warning (The default location provider determines the country visitors connect from based on their selected language. This is not very accurate, so <a target="_blank" rel="noreferrer noopener" href="https://matomo.org/docs/geo-locate/">install and use a geolocation database</a>. )
* Update over HTTPS: ok
* Mobile Messaging SMS Provider: ok
* Supports Async Archiving: No
* Async Archiving Disabled in Setting: No
* Location provider ID: default
* Location provider available: Yes
* Location provider working: Yes
* Warning Proxy header: HTTP_X_REAL_IP (A proxy header is set which means you maybe need to configure a proxy header in the Advanced settings to make location reporting work. If the location in your reports is detected correctly, you can ignore this warning. <a href="https://matomo.org/faq/wordpress/how-do-i-fix-the-proxy-header-warning-in-the-matomo-for-wordpress-system-report/" target="_blank">Learn more</a>)
* Matomo URL: Yes (https://www.bayerisches-bier.de/wp-content/plugins/matomo/app/)
## Matomo Settings
* Track mode: disabled
* Track ecommerce: Yes
* Track codeposition: footer
* Track api endpoint: default
* Track js endpoint: default
* Version history: 5.6.1
* Core version: 5.6.2
* Last tracking settings update: 1769434667
* Last settings update: 1769434667
## Logs
* Warning archive_main: 2026-01-26 14:37:07 (2 total errors during this script execution, please investigate and try and fix these errors. => CronArchive.php:546; CronArchive.php:541; CronArchive.php:252; Access.php:566; CronArchive.php:256; ScheduledTasks.php:392; class-wp-hook.php:322; class-wp-hook.php:348; plugin.php:565; wp-cron.php:191;)
* Warning archive_errors: 2026-01-26 14:37:07 ('Got invalid response from API request: ?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=year&date=2026-01-01&format=json&trigger=archivephp. Response was \'Got invalid response from API request: https://www.bayerisches-bier.de/wp-content/plugins/matomo/app/?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=year&date=2026-01-01&format=json&trigger=archivephp&. The response was empty. This usually means a server error. This solution to this error is generally to increase the value of \'memory_limit\' in your php.ini file. Please check your Web server Error Log file for more details.\'' 'Error unserializing the following response from ?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=year&date=2026-01-01&format=json&trigger=archivephp: \'Got invalid response from API request: https://www.bayerisches-bier.de/wp-content/plugins/matomo/app/?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=year&date=2026-01-01&format=json&trigger=archivephp&. The response was empty. This usually means a server error. This solution to this error is generally to increase the value of \'memory_limit\' in your php.ini file. Please check your Web server Error Log file for more details.\'' '2 total errors during this script execution, please investigate and try and fix these errors.' => ScheduledTasks.php:406; class-wp-hook.php:322; class-wp-hook.php:348; plugin.php:565; wp-cron.php:191;)
# WordPress
* Home URL: $site_url
* Site URL: $site_url
* WordPress Version: 6.4.3
* Number of blogs: 3
* Multisite Enabled: Yes
* Network Enabled: Yes
* WP_DEBUG: Yes
* WP_DEBUG_DISPLAY: No
* WP_DEBUG_LOG: Yes
* DISABLE_WP_CRON: -
* FORCE_SSL_ADMIN: Yes
* WP_CACHE: No
* CONCATENATE_SCRIPTS: -
* COMPRESS_SCRIPTS: -
* COMPRESS_CSS: -
* ENFORCE_GZIP: -
* WP_LOCAL_DEV: -
* WP_CONTENT_URL: https://www.bayerisches-bier.de/wp-content
* WP_CONTENT_DIR: $WP_CONTENT_DIR/
* UPLOADS: -
* BLOGUPLOADDIR: -
* DIEONDBERROR: -
* WPLANG: -
* ALTERNATE_WP_CRON: -
* WP_CRON_LOCK_TIMEOUT: 120
* WP_DISABLE_FATAL_ERROR_HANDLER: -
* MATOMO_SUPPORT_ASYNC_ARCHIVING: No
* MATOMO_ENABLE_TAG_MANAGER: -
* MATOMO_SUPPRESS_DB_ERRORS: -
* MATOMO_ENABLE_AUTO_UPGRADE: -
* MATOMO_DEBUG: -
* MATOMO_SAFE_MODE: -
* MATOMO_GLOBAL_UPLOAD_DIR: -
* MATOMO_LOGIN_REDIRECT: -
* Permalink Structure: /%postname%/
* Possibly uses symlink: No
* Upload base url: https://www.bayerisches-bier.de/wp-content/uploads/sites/2
* Upload base dir: $WP_CONTENT_DIR//uploads/sites/2
* Upload url: https://www.bayerisches-bier.de/wp-content/uploads/sites/2/2026/01
* Custom upload_path:
* Custom upload_url_path:
* Compatible content directory: Yes
* WP_Filesystem Initialized: Yes
* Warning System Cron Set Up: No (Warning: Your WordPress site does not appear to have a system cron job set up to run the WordPress cron. Matomo uses the WordPress cron to generate reports and to delete temporary data to provide compliance with various privacy regulations (e.g., GDPR). Without a system cron job set up, these tasks may be run irregularly or infrequently, which could lead to personal data being retained longer than allowed. To avoid this, we recommend setting up a system cron job to run the WordPress cron regularly. Contact your hosting provider if you require help with this.)
* Current User Locale: en_US
# WordPress Plugins
## MU Plugins
* ManageWP - Worker Loader: 1.0.0
## Plugins
* Advanced Custom Fields PRO: 6.2.7
* Age Gate: 2.13.6
* Borlabs Cookie: 3.3.19
* Category Order and Taxonomy Terms Order: 1.8
* Classic Editor: 1.6.3
* Contact Form 7: 5.9.3
* Contact Form CFDB7: 1.2.6.8
* de_DE: 1.0.0
* Disable Comments: 2.4.5
* Elementor: 3.20.2
* Enable Media Replace: 4.1.5
* Enhanced Media Library: 2.8.9
* Honeypot for Contact Form 7: 2.1.1
* Loco Translate: 2.6.14
* ManageWP - Worker: 4.9.28 (Network enabled)
* Matomo Analytics - Ethical Stats. Powerful Insights.: 5.6.1
* Media Sync: 1.4.1
* Modern Events Calendar Lite: 7.13.0
* OMGF: 5.8.3
* Post Types Order: 2.2
* Wordfence Security: 7.11.4 (Network enabled)
* WordPress Importer: 0.8.2
* WPCode Lite: 2.3.3
* WP Sync DB: 1.6 (Network enabled)
* WP Sync DB Media Files: 1.1.4b1 (Network enabled)
* Yoast Duplicate Post: 4.5
* Yoast SEO: 22.3
* Active Plugins: 2 (host-webfonts-local:5.8.3 insert-headers-and-footers:2.3.3)
* Theme: fp-theme (fp-theme-child)
# Server
* Server Info: Apache
* Apache AddHandler support: Supported
* PHP OS: Linux
* PHP Version: 7.4.33-nmm8
* PHP SAPI: fpm-fcgi
* PHP Binary Name: /usr/sbin/php74-fpm
* PHP Maxmind DB extension: Not loaded
* PHP Error Reporting: 0 After bootstrap: 0
* PHP Found Binary: /usr/bin/php -q
* Timezone: UTC
* WP timezone: Europe/Berlin
* Locale: de_DE_formal
* User Locale: en_US
* Memory Limit: 512M (At least 128MB recommended. Depending on your traffic 256MB or more may be needed.)
* WP Memory Limit: 512M
* WP Max Memory Limit: 512M
* Timezone version: 0.system
* Time: 1769435074
* Max Execution Time: 60
* Max Post Size: 512M
* Max Upload Size: 102400000
* Max Input Vars: 6000
* Disabled PHP functions: No
* zlib.output_compression is off: Yes
* Curl Version: 8.5.0, OpenSSL/3.0.13
* Suhosin installed: No
# PHP cli
* PHP CLI Version: 7.4.33-nmm8
* MySQLi support: ok
# Database
* MySQL Version: 5.5.5
* Mysqli Connect: Yes
* Force MySQL over Mysqli: No
* DB Prefix: wp_2_
* DB CHARSET: utf8
* DB COLLATE: utf8mb4_unicode_ci
* SHOW ERRORS: No
* SUPPRESS ERRORS: No
* Uses Socket: No
* Uses IPv6: No
* Matomo tables found: 44
* DB tables exist: Yes
* Matomo users found: 4
* Matomo sites found: 1
* Required permissions: OK
# Browser
* Browser: (Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:147.0) Gecko/20100101 Firefox/147.0)
* Language: en-us,en
And my multysite analytycs has just for ID 1 tables it seams becouse it's just show data for ID 1 in dashboard when i traing to do to 2 or 3 ID for my sub-sites it's always uses ID 1.