micpoh commented 1 year ago

I have installed Matomo with the latest version in all my projects. Up to PHP version 7.4 everything ran fine. But now when I switch to PHP version 8.0 or 8.1, no more summaries are displayed in the Worpress dashboard. If I switch back to PHP 7.4. the display works again. I have this problem in all my projects. What can I do? Matomo

mattmary commented 1 year ago

Hello @micpoh

Strange. Can't reproduce so far.

Could you post your system report please? https://matomo.org/faq/wordpress/how-do-i-find-and-copy-the-system-report-in-matomo-for-wordpress/

Do you also have any PHP or WordPress errors? Any help to understand what's going on would be appreciated

Kind regards

Mat

micpoh commented 1 year ago

Hello Mat, I don't see any errors. Here is the system report

              # Matomo

Matomo-Plugin-Version: 4.12.0
Config existiert und ist schreibbar.: Ja ("$abs_path/wp-content/uploads/matomo/config/config.ini.php" )
JS Tracker existiert und ist schreibbar.: Ja ("$abs_path/wp-content/uploads/matomo/matomo.js" )
Plugin-Verzeichnisse: Yes ([{"pluginsPathAbsolute":"$abs_path\/wp-content\/plugins\/matomo\/plugins","webrootDirRelativeToMatomo":"..\/"}])
Tmp-Verzeichnis schreibbar: Yes ($abs_path/wp-content/cache/matomo)
Matomo-Version: 4.12.3
Matomo Blog idSite: 1
Installierte Matomo-Version: 4.11.0 (Install date: 2022-10-25 16:45:03)
Upgrades outstanding: No
Upgrade in progress: No

Endpoints

Matomo JavaScript Tracker URL: ($site_url/wp-content/uploads/matomo/matomo.js)
Matomo JavaScript Tracker - WP Rest API: ($site_url/wp-json/matomo/v1/hit/)
Matomo HTTP Tracking API: ($site_url/wp-content/plugins/matomo/app/matomo.php)
Matomo HTTP Tracking API - WP Rest API: ($site_url/wp-json/matomo/v1/hit/)

Crons

Server-Zeit: 2022-11-29 17:29:56
Blog-Zeit: 2022-11-29 17:29:56 (Die nachfolgenden Daten werden in der Blog-Zeitzone angezeigt)
Sync users & sites: Next run: 2022-11-30 16:46:42 (23 Stunden 16 Minuten) ( Last started: 2022-11-29 16:46:45 (-43 Minuten 11s). Last ended: 2022-11-29 16:46:46 (-43 Minuten 10s). Interval: daily)
Archive: Next run: 2022-11-29 17:45:24 (15 Minuten 28s) ( Last started: 2022-11-29 16:45:37 (-44 Minuten 19s). Last ended: 2022-11-29 16:45:52 (-44 Minuten 4s). Interval: hourly)
Update GeoIP DB: Next run: 2022-12-24 16:46:42 (24 Tage 23 Stunden) ( Last started: 2022-11-24 16:46:51 (-5 Tage 0 Stunden). Last ended: 2022-11-24 16:46:54 (-5 Tage 0 Stunden). Interval: matomo_monthly)

Vorgeschriebene Prüfungen

PHP-Version >= : ok
PDO Erweiterung: ok
PDO\MYSQL Erweiterung: ok
MYSQLI Erweiterung: ok
Weitere erforderliche Anforderungen: ok
Erforderliche Funktionen: ok
Benötigte PHP Konfiguration (php.ini): ok
Verzeichnisse mit Schreibzugriff: ok
Verzeichnisse mit Schreibzugriff auf Tag Manager: ok

Optionale Prüfungen

64-bit PHP Binär: ok
Tracker-Status: ok
Speicherlimit: ok
Zeitzone: ok
Öffnen einer URL: ok
PageSpeed ist deaktiviert: ok
GD > 2.x + FreeType (Grafiken): ok
Andere Erweiterungen: ok
Warning Andere Funktionen: warning (shell_exec Es wird empfohlen diese eingebaute Funktion von PHP zu aktivieren. Lesen Sie folgendes, um mehr zu erfahren. set_time_limit mail parse_ini_file glob gzopen md5_file )
Dateisystem: ok
Letzter erfolgreicher Abschluss der Archivierung: ok
Datenbankfähigkeiten: ok
Maximale Packetgröße: ok
Standorterkennung: ok
Update über HTTPS: ok
Supports Async Archiving: No
Location provider ID: geoip2php
Location provider available: Yes
Location provider working: Yes
Had visit in last 5 days: Yes
Matomo URL: Yes ($site_url/wp-content/plugins/matomo/app/)

Matomo Settings

Track mode: default
Track codeposition: footer
Track api endpoint: default
Track js endpoint: default
Version history: 4.12.0, 4.11.0
Core version: 4.12.3
Last tracking settings update: 1666716393
Last settings update: 1666716393
Show get started page: 0

Logs

Keine:

WordPress

Home URL: $site_url
Site URL: $site_url
WordPress Version: 6.1.1
Number of blogs: 1
Multisite Enabled: No
Network Enabled: No
WP_DEBUG: No
WP_DEBUG_DISPLAY: No
WP_DEBUG_LOG: Yes
DISABLE_WP_CRON: No
FORCE_SSL_ADMIN: Yes
WP_CACHE: No
CONCATENATE_SCRIPTS: -
COMPRESS_SCRIPTS: -
COMPRESS_CSS: -
ENFORCE_GZIP: -
WP_LOCAL_DEV: -
WP_CONTENT_URL: $site_url/wp-content
WP_CONTENT_DIR: $abs_path/wp-content
UPLOADS: -
BLOGUPLOADDIR: -
DIEONDBERROR: -
WPLANG: -
ALTERNATE_WP_CRON: -
WP_CRON_LOCK_TIMEOUT: 60
WP_DISABLE_FATAL_ERROR_HANDLER: -
MATOMO_SUPPORT_ASYNC_ARCHIVING: -
MATOMO_TRIGGER_BROWSER_ARCHIVING: -
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: $site_url/wp-content/uploads
Upload base dir: $abs_path/wp-content/uploads
Upload url: $site_url/wp-content/uploads/2022/11
Custom upload_path:
Custom upload_url_path:
Compatible content directory: Yes

WordPress Plugins

3r Elementor Timeline Widget: 1.9
Elementor: 3.8.1
Elementor Pro: 3.8.2
Essential Addons for Elementor: 5.4.4
Matomo Analytics - Ethical Stats. Powerful Insights.: 4.12.0
OMGF: 5.4.3
Premium Addons for Elementor: 4.9.39
Premium Addons PRO: 2.8.16
Smart Slider 3: 3.5.1.12
WP-Sweep: 1.1.5
Active Plugins: 10 (3r-elementor-timeline-widget elementor-pro elementor essential-addons-for-elementor-lite host-webfonts-local matomo premium-addons-for-elementor premium-addons-pro smart-slider-3 wp-sweep)
Theme: astra (astra)

Server

Server Info: nginx/1.22.0
PHP OS: Linux
PHP Version: 7.4.30
PHP SAPI: fpm-fcgi
PHP Binary Name: php-fpm7.4
PHP Error Reporting: 0 After bootstrap: 0
Timezone: UTC
WP timezone: +00:00
Locale: de_DE
User Locale: de_DE
Memory Limit: 128M (At least 128MB recommended. Depending on your traffic 256MB or more may be needed.)
WP Memory Limit: 128M
WP Max Memory Limit: 128M
Timezone version: 0.system
Time: 1669742996
Max Execution Time: 300
Max Post Size: 2000M
Max Upload Size: 2097152000
Max Input Vars: 10000
Disabled PHP functions: Yes (pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,php_uname,getmyuid,getmypid,passthru,leak,listen,diskfreespace,link,ignore_user_abord,shell_exec,dl,exec,system,highlight_file,source,show_source,fpaththru,virtual,posix_ctermid,posix_getcwd,posix_getegid,posix_geteuid,posix_getgid,posix_getgrgid,posix_getgrnam,posix_getgroups,posix_getlogin,posix_getpgid,posix_getpgrp,posix_getpid,posix,_getppid,posix_getpwnam,posix_getpwuid,posix_getrlimit,posix_getsid,posix_getuid,posix_isatty,posix_kill,posix_mkfifo,posix_setegid,posix_seteuid,posix_setgid,posix_setpgid,posix_setsid,posix_setuid,posix_times,posix_ttyname,posix_uname,proc_open,proc_close,proc_get_status,proc_nice,proc_terminate,popen,putenv)
zlib.output_compression is off: Yes
Curl Version: 7.58.0, OpenSSL/1.1.1j
Suhosin installed: No

Database

MySQL Version: 5.5.5
Mysqli Connect: Yes
Force MySQL over Mysqli: No
DB Prefix: wpqivhvbnwxn
DB CHARSET: utf8
DB COLLATE:
SHOW ERRORS: No
SUPPRESS ERRORS: No
Uses Socket: No
Uses IPv6: No
Matomo tables found: 61
DB tables exist: Yes
Matomo users found: 2
Matomo sites found: 1
Erforderliche Berechtigungen: OK

Browser

Browser: (Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:107.0) Gecko/20100101 Firefox/107.0)
Language: de,en-us,en

mattmary commented 1 year ago

Hello @micpoh

Just to be sure, when you say you have no data in your summary graphs, it means that for all of your dates you don't have data? Or you have data for some dates and for the other ones it's empty? It looks like in your screenshot that it's only concern some specific dates?

Do you encounter any error when accessing your Matomo instance ("Matomo Analytics > Reporting" menu)? Kind regards

Mat

micpoh commented 1 year ago

Hello Mat,

unfortunately, I can only contact you again now, because I was on the road for a few days. I have now changed the PHP version on several consecutive days and made screenshots:

Until December 10. PHP version 7.4 was set. The display was okay. See image "PHP 5.-10.12.jpg".
On 10. December I changed to PHP version 8.1. around noon. In the following days no more evaluation was displayed. See image "PHP 10.-13.12.jpg".
On December 13th I switched back to PHP version 7.4. The display is now okay again, even for the days that were not displayed with PHP version 8.1, e.g. December 11 and 12. See image "PHP 14.12.jpg".

I also don't see any error message anywhere.

Kind regards, Michael

PHP 5 -10 12

PHP 10 -13 12

PHP 14 12

mattmary commented 1 year ago

Hello @micpoh

It's very strange, our plugin has been tested with these versions. I can see from your hosting interface that you can access to the php error log. Would you mind email it wordpress@matomo.org? Kind regards

Mat

micpoh commented 1 year ago

2022/12/14 19:28:44 [crit] 9314#9314: *326272 SSL_do_handshake() failed (SSL: error:141CF06C:SSL routines:tls_parse_ctos_key_share:bad key share) while SSL handshaking, client: 134.209.0.0, server: 157.90.0.0:443

2022/12/14 16:08:11 [crit] 9314#9314: 324336 SSL_do_handshake() failed (SSL: error:141CF06C:SSL routines:tls_parse_ctos_key_share:bad key share) while SSL handshaking, client: 212.102.0.0 server: 157.90.0.0:443 2022/12/14 15:03:54 [crit] 9314#9314: 323743 SSL_do_handshake() failed (SSL: error:141CF06C:SSL routines:tls_parse_ctos_key_share:bad key share) while SSL handshaking, client: 192.241.0.0, server: 157.90.0.0:443 2022/12/14 12:56:22 [error] 9314#9314: 322449 directory index of "/home/wp/disk/wordpress/wp-admin/css/" is forbidden, client: 43.130.0.0, server: sg-wissmar.de, request: "GET /wp-admin/css/ HTTP/1.1", host: "sg-wissmar.de", referrer: "o.com" 2022/12/14 12:48:23 [crit] 9314#9314: 322358 SSL_do_handshake() failed (SSL: error:141CF06C:SSL routines:tls_parse_ctos_key_share:bad key share) while SSL handshaking, client: 154.89.0.0, server: 157.90.0.0:0 2022/12/14 11:09:51 [error] 9314#9314: 320923 FastCGI sent in stderr: "PHP message: [sg-wissmar.de] Error in Matomo: This feature is not available" while reading response header from upstream, client: 157.90.0.0, server: sg-wissmar.de, request: "GET /wp-content/plugins/matomo/app/?module=Installation&action=getEmptyPageForSystemCheck HTTP/1.1", upstream: "fastcgi://unix:/var/run/wordpress.php-fpm.sock:", host: "sg-wissmar.de", referrer: "https://sg-wissmar.de/wp-content/plugins/matomo/app/?module=Installation&action=getEmptyPageForSystemCheck" 2022/12/14 11:08:36 [error] 9314#9314: 320902 FastCGI sent in stderr: "PHP message: [sg-wissmar.de] Error in Matomo: This feature is not available" while reading response header from upstream, client: 157.90.0.0, server: sg-wissmar.de, request: "GET /wp-content/plugins/matomo/app/?module=Installation&action=getEmptyPageForSystemCheck HTTP/1.1", upstream: "fastcgi://unix:/var/run/wordpress.php-fpm.sock:", host: "sg-wissmar.de", referrer: "https://sg-wissmar.de/wp-content/plugins/matomo/app/?module=Installation&action=getEmptyPageForSystemCheck" 2022/12/14 06:20:10 [crit] 9314#9314: *318465 SSL_do_handshake() failed (SSL: error:141CF06C:SSL routines:tls_parse_ctos_key_share:bad key share) while SSL handshaking, client: 74.82.0.0, server: 157.90.0.0:443

mattmary commented 1 year ago

Hello @micpoh

Thank you. Nothing for the date you changed your PHP version? Kind regards

micpoh commented 1 year ago

Yesterday (December 15) I switched to PHP 8.1. These are the error messages from today (December 16)

2022/12/16 19:47:09 [error] 9314#9314: 356050 FastCGI sent in stderr: "PHP message: PHP Warning: Trying to access array offset on value of type null in /home/wp/disk/wordpress/wp-content/plugins/elementor-pro/modules/nav-menu/widgets/nav-menu.php on line 1453PHP message: PHP Warning: Trying to access array offset on value of type null in /home/wp/disk/wordpress/wp-content/plugins/elementor-pro/modules/nav-menu/widgets/nav-menu.php on line 1466PHP message: PHP Warning: Trying to access array offset on value of type null in /home/wp/disk/wordpress/wp-content/plugins/elementor-pro/modules/nav-menu/widgets/nav-menu.php on line 1477PHP message: PHP Warning: Trying to access array offset on value of type null in /home/wp/disk/wordpress/wp-content/plugins/elementor-pro/modules/nav-menu/widgets/nav-menu.php on line 1490PHP message: PHP Warning: Trying to access array offset on value of type null in /home/wp/disk/wordpress/wp-content/plugins/elementor-pro/modules/nav-menu/widgets/nav-menu.php on line 1453PHP message: PHP Warning: Trying to access array offset on value of type null in /home/wp/disk/wordpress/wp-content/plugins/elementor-pro/modules/nav-menu/widgets/nav-menu.php on line 1466PHP message: PHP Warning: Trying to access array offset on value of type null in /home/wp/disk/wordpress/wp-content/plugins/elementor-pro/modules/nav-menu/widgets/nav-menu.php on line 1477PHP message: PHP Warning: Trying to access array offset on value of type null in /home/wp/disk/wordpress/wp-content/plugins/elementor-pro/modules/nav-menu/widgets/nav-menu.php on line 1490", client: 95.223.184.186, server: sg-wissmar.de, request: "GET /sparte-koronar/ HTTP/2.0", host: "sg-wissmar.de", referrer: "https://sg-wissmar.de/" 2022/12/16 19:47:05 [error] 9314#9314: 356050 FastCGI sent in stderr: "PHP message: PHP Warning: Trying to access array offset on value of type null in /home/wp/disk/wordpress/wp-content/plugins/elementor-pro/modules/nav-menu/widgets/nav-menu.php on line 1453PHP message: PHP Warning: Trying to access array offset on value of type null in /home/wp/disk/wordpress/wp-content/plugins/elementor-pro/modules/nav-menu/widgets/nav-menu.php on line 1466PHP message: PHP Warning: Trying to access array offset on value of type null in /home/wp/disk/wordpress/wp-content/plugins/elementor-pro/modules/nav-menu/widgets/nav-menu.php on line 1477PHP message: PHP Warning: Trying to access array offset on value of type null in /home/wp/disk/wordpress/wp-content/plugins/elementor-pro/modules/nav-menu/widgets/nav-menu.php on line 1490PHP message: PHP Warning: Trying to access array offset on value of type null in /home/wp/disk/wordpress/wp-content/plugins/elementor-pro/modules/nav-menu/widgets/nav-menu.php on line 1453PHP message: PHP Warning: Trying to access array offset on value of type null in /home/wp/disk/wordpress/wp-content/plugins/elementor-pro/modules/nav-menu/widgets/nav-menu.php on line 1466PHP message: PHP Warning: Trying to access array offset on value of type null in /home/wp/disk/wordpress/wp-content/plugins/elementor-pro/modules/nav-menu/widgets/nav-menu.php on line 1477PHP message: PHP Warning: Trying to access array offset on value of type null in /home/wp/disk/wordpress/wp-content/plugins/elementor-pro/modules/nav-menu/widgets/nav-menu.php on line 1490", client: 95.223.184.186, server: sg-wissmar.de, request: "GET / HTTP/2.0", host: "sg-wissmar.de" 2022/12/16 19:09:46 [error] 9314#9314: 355511 FastCGI sent in stderr: "PHP message: PHP Warning: Trying to access array offset on value of type null in /home/wp/disk/wordpress/wp-content/plugins/elementor-pro/modules/nav-menu/widgets/nav-menu.php on line 1453PHP message: PHP Warning: Trying to access array offset on value of type null in /home/wp/disk/wordpress/wp-content/plugins/elementor-pro/modules/nav-menu/widgets/nav-menu.php on line 1466PHP message: PHP Warning: Trying to access array offset on value of type null in /home/wp/disk/wordpress/wp-content/plugins/elementor-pro/modules/nav-menu/widgets/nav-menu.php on line 1477PHP message: PHP Warning: Trying to access array offset on value of type null in /home/wp/disk/wordpress/wp-content/plugins/elementor-pro/modules/nav-menu/widgets/nav-menu.php on line 1490PHP message: PHP Warning: Trying to access array offset on value of type null in /home/wp/disk/wordpress/wp-content/plugins/elementor-pro/modules/nav-menu/widgets/nav-menu.php on line 1453PHP message: PHP Warning: Trying to access array offset on value of type null in /home/wp/disk/wordpress/wp-content/plugins/elementor-pro/modules/nav-menu/widgets/nav-menu.php on line 1466PHP message: PHP Warning: Trying to access array offset on value of type null in /home/wp/disk/wordpress/wp-content/plugins/elementor-pro/modules/nav-menu/widgets/nav-menu.php on line 1477PHP message: PHP Warning: Trying to access array offset on value of type null in /home/wp/disk/wordpress/wp-content/plugins/elementor-pro/modules/nav-menu/widgets/nav-menu.php on line 1490", client: 194.187.171.93, server: sg-wissmar.de, request: "GET / HTTP/2.0", host: "sg-wissmar.de" 2022/12/16 19:05:09 [error] 9314#9314: 355466 FastCGI sent in stderr: "PHP message: PHP Warning: Trying to access array offset on value of type null in /home/wp/disk/wordpress/wp-content/plugins/elementor-pro/modules/nav-menu/widgets/nav-menu.php on line 1453PHP message: PHP Warning: Trying to access array offset on value of type null in /home/wp/disk/wordpress/wp-content/plugins/elementor-pro/modules/nav-menu/widgets/nav-menu.php on line 1466PHP message: PHP Warning: Trying to access array offset on value of type null in /home/wp/disk/wordpress/wp-content/plugins/elementor-pro/modules/nav-menu/widgets/nav-menu.php on line 1477PHP message: PHP Warning: Trying to access array offset on value of type null in /home/wp/disk/wordpress/wp-content/plugins/elementor-pro/modules/nav-menu/widgets/nav-menu.php on line 1490PHP message: PHP Warning: Trying to access array offset on value of type null in /home/wp/disk/wordpress/wp-content/plugins/elementor-pro/modules/nav-menu/widgets/nav-menu.php on line 1453PHP message: PHP Warning: Trying to access array offset on value of type null in /home/wp/disk/wordpress/wp-content/plugins/elementor-pro/modules/nav-menu/widgets/nav-menu.php on line 1466PHP message: PHP Warning: Trying to access array offset on value of type null in /home/wp/disk/wordpress/wp-content/plugins/elementor-pro/modules/nav-menu/widgets/nav-menu.php on line 1477PHP message: PHP Warning: Trying to access array offset on value of type null in /home/wp/disk/wordpress/wp-content/plugins/elementor-pro/modules/nav-menu/widgets/nav-menu.php on line 1490", client: 161.35.162.74, server: sg-wissmar.de, request: "GET / HTTP/1.1", host: "sg-wissmar.de", referrer: "http://157.90.228.210/"

micpoh commented 1 year ago

I had switched back to PHP 8.1 on December 15. Now I have an error message. Maybe this helps. Error

mattmary commented 1 year ago

Hello @micpoh

The errors you highlight concern your elementor-pro plugin, not the Matomo one. You can submit a bug report here: https://elementor.com/help/how-can-i-report-on-issues-conflicts/

But if your archiving process still fails, you may have a message in the log part of your system report. Do you have one? If yes, could you please post it here. With PHP 8.1, do you also have an error when forcing the archiving process from the "Matomo Analytics > Diagnostics > Troubeshooting > Archive reports" menu? Kind regards

Mat

micpoh commented 1 year ago

I have now tried to do the archiving manually and got the following error

JSON Error

mattmary commented 1 year ago

Hello @micpoh

And nothing in the log part of your system report?

As a workaround, you could try to disable the schedule archiving and set it up to be executed when you display a Matomo page. To do so, please add the following lines in your wp-config.php file:

if (!defined('MATOMO_SUPPORT_ASYNC_ARCHIVING')) {
    define('MATOMO_SUPPORT_ASYNC_ARCHIVING', false);
}

Please let me know if after setting this constant you are able to view your reports in Matomo. Kind regards

Mat

micpoh commented 1 year ago

I have not seen any other error messages.

Unfortunately I am not a professional, but only a lateral and therefore Ido not know anything about changing the wp-config.php. Therefore, I can not include this unfortunately. What can I do instead?

mattmary commented 1 year ago

Hello @micpoh

Do you have a shell access on your webserver?

micpoh commented 1 year ago

what is "shell access"? Access via Filezilla?

mattmary commented 1 year ago

Hello @micpoh

A shell access is a remote access to your webserver. It's not a big problem if you don't have one.

Here's a tutorial on how to edit the wp-config.php file: https://www.wpbeginner.com/beginners-guide/how-to-edit-wp-config-php-file-in-wordpress/ You'll just have to copy paste the lines I gave you within this file.

Kind regards

Mat

micpoh commented 1 year ago

I have added the lines to wp-config.php. Nevertheless, no evaluations are displayed for the days in which I switched to PHP 8.1. Is there anything else I need to do so that something is displayed?

mattmary commented 1 year ago

Hello @micpoh

After adding these lines, did you go to Matomo and ask a page for these dates? Otherwise, the reports are still not generated. Kind regards

Mat

micpoh commented 1 year ago

What exactly does "ask for a page" mean?

When I click on "yesterday", "today" or "this week" nothing happens, the data are still not displayed. After that I clicked on "Berichte archivieren" in Diagnose/Troubelshooting. There came again the already described error "...JSON.parse ... But when I went back to the summary the report is displayed now.

okay

But this can not be the solution that I have to enter these lines everywhere in the wp-config.php. Something must be the cause that the reports are not displayed "in the normal way".

mattmary commented 1 year ago

Hello @micpoh

You have definitively an archiving problem. This is confirmed by the steps you've made:

You've disabled the asynchrony archiving process by adding this constant in your wp-config.php file.
Nothing was available in your widget
You've opened a page in your Matomo: the archiving process has been made then
Then you have now data in your widget.

Unfortunately, without any additional details (PHP errors log, WordPress error log) I can't help you to fix this issue: archiving error mostly come from incompatible plugins, but can come also from custom PHP configuration. You have a lot of errors in your log files: some related to your SSL configuration, some related to your Elementor pro plugin, and one related to Matomo (which might not explain your archiving error problem).

To go further, I would invite you to fix all the non Matomo errors. You can for example submit a bug report to the Elementor support, they should fix it quickly. From the Matomo point of view, I have for now not enough information to identify what leads to this error you have. Are you familiar with patching a file? Otherwise, I'll give you a file to replace; we should then get more information about the requested action which fails.

You can also email me your full WordPress and PHP error logs files to wordpress@matomo.org. I'll study them. Please also notify me when you've switched back to PHP 8.1. Please be sure to also email me the PHP error log for your PHP cli: depending on your configuration, it can be different from your webserver one. Your hosting provider can help you in this task.

Kind regards

Mat

micpoh commented 1 year ago

I had PHP 8.1 set all the time.

In the general error log I have the following error messages. Does this help a bit?

2022/12/22 12:15:13 [error] 9314#9314: 433337 FastCGI sent in stderr: "Unable to open primary script: /home/wp/disk/wordpress/assets/fileupload/server/php/index.php (No such file or directory)" while reading response header from upstream, client: 194.38.0.0, server: sg-wissmar.de, request: "GET /assets/fileupload/server/php/index.php?file=tf2rghf.jpg HTTP/1.1", upstream: "fastcgi://unix:/var/run/wordpress.php-fpm.sock:", host: "sg-wissmar.de" 2022/12/22 11:24:55 [error] 9314#9314: 432820 FastCGI sent in stderr: "PHP message: PHP Deprecated: version_compare(): Passing null to parameter #1 ($version1) of type string is deprecated in /home/wp/disk/wordpress/wp-content/plugins/matomo/app/plugins/Diagnostics/Diagnostic/PhpVersionCheck.php on line 56PHP message: PHP Deprecated: Return type of Requests_Cookie_Jar::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wp/disk/wordpress/wp-includes/Requests/Cookie/Jar.php on line 63PHP message: PHP Deprecated: Return type of Requests_Cookie_Jar::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wp/disk/wordpress/wp-includes/Requests/Cookie/Jar.php on line 73PHP message: PHP Deprecated: Return type of Requests_Cookie_Jar::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wp/disk/wordpress/wp-includes/Requests/Cookie/Jar.php on line 89PHP message: PHP Deprecated: Return type of Requests_Cookie_Jar::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wp/disk/wordpress/wp-includes/Requests/Cookie/Jar.php on line 102PHP message: PHP Deprecated: Return type of Requests_Cookie_Jar::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wp/disk/wordpress/wp-includes/Requests/Cookie/Jar.php on line 111PHP message: PHP Deprecated: Return type of Requests_Utility_CaseInsensitiveD 2022/12/22 11:24:55 [error] 9314#9314: 432825 FastCGI sent in stderr: "PHP message: [sg-wissmar.de] Error in Matomo: This feature is not available" while reading response header from upstream, client: 157.90.0.0, server: sg-wissmar.de, request: "GET /wp-content/plugins/matomo/app/?module=Installation&action=getEmptyPageForSystemCheck HTTP/1.1", upstream: "fastcgi://unix:/var/run/wordpress.php-fpm.sock:", host: "sg-wissmar.de", referrer: "https://sg-wissmar.de/wp-content/plugins/matomo/app/?module=Installation&action=getEmptyPageForSystemCheck" 2022/12/22 11:24:13 [crit] 9314#9314: 432814 SSL_do_handshake() failed (SSL: error:141CF06C:SSL routines:tls_parse_ctos_key_share:bad key share) while SSL handshaking, client: 64.62.0.0, server: 157.90.0.0:443 2022/12/22 11:21:54 [error] 9314#9314: *432770 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 114.119.137.51, server: sg-wissmar.de, request: "GET /azo9f1/liste-swarovski-figuren-1219b6 HTTP/1.1", upstream: "fastcgi://unix:/var/run/wordpress.php-fpm.sock", host: "sg-wissmar.de", referrer: "http://sg-wissmar.de/azo9f1/rundreise-porto%2C-lissabon-1219b6"

mattmary commented 1 year ago

Ref https://github.com/matomo-org/matomo/issues/19352 Ref https://github.com/matomo-org/matomo/issues/20134

mattmary commented 1 year ago

Hello @micpoh

Thank you. The two related Matomo issues can't explain why your archiving is not working. Anyway, I've created two issues in Matomo to let them fixed in the next release. Is it your full PHP error log file? The archiving process happens hourly, so if there is an error, it might not be in these lines.

Could you also enable the Matomo debug? (WP_DEBUG, WP_DEBUG_LOG and MATOMO_DEBUG constants)? https://matomo.org/faq/wordpress/i-have-a-problem-how-do-i-troubleshoot-and-enable-wp_debug/

Kind regards

Mat

micpoh commented 1 year ago

Today I did the following:

PHP is still on 8.1
deleted the additional entry in wp-config.php
nothing was shown in the summary for the 22nd/23rd at first (image summary-before.jpg)
i triggered "archive reports" in troubleshooting.
the known "JSON" error occurred
nevertheless, something was now displayed in the summary (even without the additional text in wp-config.php!): image summary-after.jpg

I just saw that in the last message in Github you had still written that I should add something in the wp-config.php (these lines were not included in my email). I created the entries and did the above process again. Here is the full error log.

2022/12/23 11:41:45 [error] 9314#9314: 450464 FastCGI sent in stderr: "PHP message: PHP Warning: Constant WP_DEBUG already defined in /home/wp/disk/wordpress/wp-config.php on line 53PHP message: PHP Warning: Constant WP_DEBUG_LOG already defined in /home/wp/disk/wordpress/wp-config.php on line 54" while reading response header from upstream, client: 95.223.185.148, server: sg-wissmar.de, request: "POST /wp-admin/admin-ajax.php HTTP/2.0", upstream: "fastcgi://unix:/var/run/wordpress.php-fpm.sock:", host: "xxx.de", referrer: "https://sg-wissmar.de/wp-admin/admin.php?page=matomo-summary" 2022/12/23 11:39:58 [error] 9314#9314: 450239 FastCGI sent in stderr: "PHP message: PHP Warning: Constant WP_DEBUG already defined in /home/wp/disk/wordpress/wp-config.php on line 53PHP message: PHP Warning: Constant WP_DEBUG_LOG already defined in /home/wp/disk/wordpress/wp-config.php on line 54" while reading response header from upstream, client: 159.69.219.136, server: xxx.de, request: "GET /category/yyyy/feed/ HTTP/1.1", upstream: "fastcgi://unix:/var/run/wordpress.php-fpm.sock:", host: "xxx.de" 2022/12/23 11:39:58 [error] 9314#9314: 450239 FastCGI sent in stderr: "PHP message: PHP Warning: Constant WP_DEBUG already defined in /home/wp/disk/wordpress/wp-config.php on line 53PHP message: PHP Warning: Constant WP_DEBUG_LOG already defined in /home/wp/disk/wordpress/wp-config.php on line 54" while reading response header from upstream, client: 159.69.219.136, server: xxx.de, request: "GET /robots.txt HTTP/1.1", upstream: "fastcgi://unix:/var/run/wordpress.php-fpm.sock:", host: "xxx.de" 2022/12/23 11:39:45 [error] 9314#9314: 450205 FastCGI sent in stderr: "PHP message: PHP Warning: Constant WP_DEBUG already defined in /home/wp/disk/wordpress/wp-config.php on line 53PHP message: PHP Warning: Constant WP_DEBUG_LOG already defined in /home/wp/disk/wordpress/wp-config.php on line 54" while reading response header from upstream, client: 95.223.185.148, server: xxx.de, request: "POST /wp-admin/admin-ajax.php HTTP/2.0", upstream: "fastcgi://unix:/var/run/wordpress.php-fpm.sock:", host: "xxx.de", referrer: "https://xxx.de/wp-admin/admin.php?page=matomo-summary" 2022/12/23 11:38:44 [error] 9314#9314: 450034 FastCGI sent in stderr: "PHP message: PHP Warning: Constant WP_DEBUG already defined in /home/wp/disk/wordpress/wp-config.php on line 53PHP message: PHP Warning: Constant WP_DEBUG_LOG already defined in /home/wp/disk/wordpress/wp-config.php on line 54" while reading response header from upstream, client: 95.223.185.148, server: sg-wissmar.de, request: "GET /wp-admin/admin.php?page=matomo-summary HTTP/2.0", upstream: "fastcgi://unix:/var/run/wordpress.php-fpm.sock:", host: "xxx.de", referrer: "https://xxx.de/wp-admin/admin.php?page=matomo-systemreport&tab=troubleshooting" 2022/12/23 11:38:40 [error] 9314#9314: 450034 FastCGI sent in stderr: "PHP message: PHP Warning: Constant WP_DEBUG already defined in /home/wp/disk/wordpress/wp-config.php on line 53PHP message: PHP Warning: Constant WP_DEBUG_LOG already defined in /home/wp/disk/wordpress/wp-config.php on line 54" while reading response header from upstream, client: 95.223.0.0, server: xxx.de, request: "GET /wp-admin/admin.php?page=matomo-systemreport&tab=troubleshooting HTTP/2.0", upstream: "fastcgi://unix:/var/run/wordpress.php-fpm.sock:", host: "xxx.de", referrer: "https://xxx.de/wp-admin/admin.php?page=matomo-systemreport" 2022/12/23 11:38:36 [error] 9314#9314: 450034 FastCGI sent in stderr: "PHP message: PHP Warning: Constant WP_DEBUG already defined in /home/wp/disk/wordpress/wp-config.php on line 53PHP message: PHP Warning: Constant WP_DEBUG_LOG already defined in /home/wp/disk/wordpress/wp-config.php on line 54" while reading response header from upstream, client: 95.223.0.0, server: xxx.de, request: "POST /wp-admin/admin.php?page=matomo-systemreport&tab=troubleshooting HTTP/2.0", upstream: "fastcgi://unix:/var/run/wordpress.php-fpm.sock:", host: "sg-wissmar.de", referrer: "https://xxx.de/wp-admin/admin.php?page=matomo-systemreport&tab=troubleshooting" 2022/12/23 11:38:31 [error] 9314#9314: 450034 FastCGI sent in stderr: "PHP message: PHP Warning: Constant WP_DEBUG already defined in /home/wp/disk/wordpress/wp-config.php on line 53PHP message: PHP Warning: Constant WP_DEBUG_LOG already defined in /home/wp/disk/wordpress/wp-config.php on line 54" while reading response header from upstream, client: 95.223.0.0, server: xxx.de, request: "GET /wp-admin/admin.php?page=matomo-systemreport&tab=troubleshooting HTTP/2.0", upstream: "fastcgi://unix:/var/run/wordpress.php-fpm.sock:", host: "xxx.de", referrer: "https://xxx.de/wp-admin/admin.php?page=matomo-systemreport"

Summary before Summary after

But I also have another problem with Matomo, but not with this website, but with another one. I actually wanted to report the error only when the current problem is solved. But maybe this will help with troubleshooting.

In two of my projects the following error appears in the frontend: see "zzz.jpg" (https://zzz.de/).

zzz

To find the error I did the following. I disabled all "experiments" in wordpress/elementor. After that the error did not occur. Then I enabled the "experiments" one by one again (as the settings were before). When I enabled "Page Transitions" again, the error occurred again. On this website (https://zzz.de/) I use "Page Transitions", on the website of the original error (https://xxx.de/) "Page Transitions" is enabled, but I don't use it. After I located where the error comes from, I deactivated my plugins one by one. When I disabled Matomo, the error no longer occurred. So on the https://rad-stall.de/ website, Matomo causes an error when "Page Transitions" is enabled and also used.

I wrote this just for your information, so that you can investigate if this new problem is possibly also related to the original problem.

mattmary commented 1 year ago

Hello @micpoh

It seems that you already have the debug constants in your wp-config.php file: Some errors are risen in your php.log file telling so. You can remove the lines I asked you to add, it seems your configuration log at least the content. You should have in this configuration a wp-content/debug.log file. Could you post it when you are in PHP 8.1 configuration?

Would you mind reproduce this JSON error and give me the output of your Rohdaten tab please? There might be an error message within.

Additionally, for your other problem, could you create another issue and posting your system report please? Thanks in advance

Kind regards

Mat

micpoh commented 1 year ago

WP Debug is deactivated for me ... grafik

Here is the content of my Rohdaten tab:

<!DOCTYPE html> <html class="wp-toolbar" lang="de-DE">

Diagnose ‹ SG Wißmar — WordPress

Diagnose

System report Troubleshooting

Problembehandlung

Wie können wir helfen?

Benutzerhandbücher - Lerne, wie du Matomo konfigurierst und deine Daten effektiv analysierst
Matomo für WordPress FAQs - Erhalte Antworten auf häufig gestellte Fragen
Allgemeine FAQs - Erhalte Antworten auf häufig gestellte Fragen
Foren - Erhalte Hilfe direkt von der Matomo-Benutzer-Community
Glossar - Erfahre mehr über häufig verwendete Begriffe, um das Beste aus Matomo Analytics herauszuholen
Support-Tarife - Lass dich online von unserem erfahrenen Team beraten, wie du Matomo am besten nutzen kannst

Beliebte FAQs zur Problembehandlung

Möchtest du einen Fehler melden oder hast du eine Funktionsanforderung?

Bitte lies die Empfehlungen zum Schreiben eines guten Fehlerberichts oder einer Funktionsanforderung. Registriere dich dann oder melde dich bei unserem Problem-Tracker an und erstell einen neuen Problembericht.

Bevor du eine Problemmeldung erstellst

Falls du irgendein Problem in Matomo hast, ist es immer eine gute Idee, zuerst deine Webserver-Protokolle (wenn möglich) auf Fehler zu überprüfen.
Vielleicht möchtest du auch WP_DEBUG aktivieren. Um Probleme zu debuggen, die im Hintergrund auftreten, z. B. die Berichterstellung während eines Cronjobs, kannst du auch WP_DEBUG_LOG aktivieren.

Hast du Leistungsprobleme?

Vielleicht möchtest du DISABLE_WP_CRON in deiner wp-config.php deaktivieren und einen tatsächlichen Cronjob einrichten, sowie unsere empfohlene Servergröße ansehen.

If your website gets a lot of traffic we recommend installing Matomo On-Premise separately (it's free as well) in combination with the WP-Matomo WordPress plugin. It's free to install and has the same requirements as WordPress. Your Matomo will then run a lot faster and it allows you to put your Matomo installation on a separate server if needed.

Don't want all the hassle of maintaining a Matomo? Sign up for a free Matomo Cloud trial. We can migrate all your data onto our Cloud for free. 100% data ownership guaranteed.

mattmary commented 1 year ago

Hi @micpoh

Thank you.

I can't find any error message in the output you provided. But maybe I'm wrong? Does this output come from your browser developer tools? If not, may I ask you to give me the output of the query which fails in a JSON error?

You can open your browser developer tools in Chrome, in Firefox When opened, you'll have a Network tab: open the troubleshooting page, then click the archive reports button. You might have in this network tab a query which fails with a 40x or 50x error code. Please click on it, and in the right part you'll have a panel like this one:

Screenshot from 2023-01-10 13-04-55

On Firefox, there is a raw button: please enable it.

And then could you copy paste this response?

Sorry for this inconvenience. And thanks in advance Kind regards

Mat

micpoh commented 1 year ago

The content from the last post was directly from Matomo from the "Rohdaten" tab. After the JSON error was output, I clicked the "Rohdaten" tab and posted the entire content.

grafik

I have now tried in Firefox to reproduce what you wrote to me. My browser developer tool look a little different. That's why I created a little movie. Please have a look if the procedure was okay like that and if you can do something with it. https://www.loom.com/share/5f905953c7924476993bdfb8f719cc18

mattmary commented 1 year ago

Hello @micpoh

Thank you for your screencast.

I'm wondering if you would accept to create us an account in your WordPress? (when you are in PHP 8.1 configuration): it would make this investigation faster. If yes, would you mind sending the credentials to wordpress@matomo.org?

Additionally, could you also post your system report when you use PHP 8 please?

Kind regards

Mat

mattmary commented 1 year ago

May be related to this one too? https://github.com/matomo-org/matomo-for-wordpress/issues/660 this is the same hosting provider.

mattmary commented 1 year ago

Hello @micpoh

Thank you for the access you provided us in the topic https://secure.helpscout.net/conversation/2127344172/3273066?folderId=4753515 I'll not update anything in your back office, no worries.

mattmary commented 1 year ago

Hello @micpoh

Just wondering if your HTTP_AUTH could block your archiving requests? (You are in the mode that is a CURL request which realise your archiving process): We do not provide any credentials when running the CURL request.

Maybe in your PHP 7.4 configuration the http authentication does not exist?

Could you ask your hosting provider to disable the http authentication when requests are coming from the localhost address?

Kind regards

Mat

micpoh commented 1 year ago

Hello Mat,

I disabled http authentication the day before yesterday. I did the same for additional testing in another project where I have the same problem. From the looks of it, that didn't work though. Still no evaluations are displayed. You can have a look at it yourself.

Kind regards

Michael Pohl

From: mattmary Sent: Wednesday, January 18, 2023 11:22 PM To: matomo-org/matomo-for-wordpress Cc: micpoh ; Mention Subject: Re: [matomo-org/matomo-for-wordpress] Partial data in the WordPress widgets after switching to PHP 8.0/8.1 (Issue #676)

Hello @micpoh

Just wondering if your HTTP_AUTH could block your archiving requests? (You are in the mode that is a CURL request which realise your archiving process): We do not provide any credentials when running the CURL request.

Maybe in your PHP 7.4 configuration the http authentication does not exist?

Could you ask your hosting provider to disable the http authentication when requests are coming from the localhost address?

Kind regards

Mat

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>

mattmary commented 1 year ago

Hello @micpoh

So I confirm that your problem is an archiving problem when you swtich to PHP8. I have to understand why you don't have any exception thrown when running the archiving process. Maybe I'll get more information in your log files.

Could you add in your wp-config.php file the following content:

if (!defined('MATOMO_DEBUG')) {
    define('MATOMO_DEBUG', true);
}
if (!defined('MATOMO_SUPPORT_ASYNC_ARCHIVING')) {
    define('MATOMO_SUPPORT_ASYNC_ARCHIVING', false);
}

I don't know your hosting provider and especially their configuration interface: maybe you are able to enable the WordPress debug mode directly from its interface? If this is the case, would you mind enable it too? Otherwise, instead of these lines above, you should add in your wp-config.php file the following content:

if (!defined('WP_DEBUG')) {
    define('WP_DEBUG', true);
}
if (!defined('MATOMO_DEBUG')) {
    define('MATOMO_DEBUG', true);
}
if (!defined('MATOMO_SUPPORT_ASYNC_ARCHIVING')) {
    define('MATOMO_SUPPORT_ASYNC_ARCHIVING', false);
}

We'll also publish a new plugin release either today or early next week. Could you upgrade it then?

Thanks in advance

Kind regards

Mat

Note: I've tried to access your debug log file (http://yourhost/wp-content/debug.log), but your hosting provider has restricted his access. Do you have any option to allow a DDNS name to access this file?

micpoh commented 1 year ago

Hello Mat,

I have added the first text to wp-config.php.

Also I have activated the WordPress debug mode. Write me if you want me to send you the contents of the log file.

Kind regards, Michael

From: mattmary Sent: Thursday, January 26, 2023 9:09 PM To: matomo-org/matomo-for-wordpress Cc: micpoh ; Mention Subject: Re: [matomo-org/matomo-for-wordpress] Partial data in the WordPress widgets after switching to PHP 8.0/8.1 (Issue #676)

Hello @micpoh

So I confirm that your problem is an archiving problem when you swtich to PHP8. I have to understand why you don't have any exception thrown when running the archiving process. Maybe I'll get more information in your log files.

Could you add in your wp-config.php file the following content:

if (!defined('MATOMO_DEBUG')) { define('MATOMO_DEBUG', true); } if (!defined('MATOMO_SUPPORT_ASYNC_ARCHIVING')) { define('MATOMO_SUPPORT_ASYNC_ARCHIVING', false); } I don't know your hosting provider and especially their configuration interface: maybe you are able to enable the WordPress debug mode directly from its interface? If this is the case, would you mind enable it too? Otherwise, instead of these lines above, you should add in your wp-config.php file the following content:

if (!defined('WP_DEBUG')) { define('WP_DEBUG', true); } if (!defined('MATOMO_DEBUG')) { define('MATOMO_DEBUG', true); } if (!defined('MATOMO_SUPPORT_ASYNC_ARCHIVING')) { define('MATOMO_SUPPORT_ASYNC_ARCHIVING', false); } We'll also publish a new plugin release either today or early next week. Could you upgrade it then?

Thanks in advance

Kind regards

Mat

Note: I've tried to access your debug log file (http://yourhost/wp-content/debug.log), but your hosting provider has restricted his access. Do you have any option to allow a DDNS name to access this file?

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>

mattmary commented 1 year ago

Hello @micpoh

With all the information you provided and after our investigations, we have not been able to reproduce your bug. Just wondering if you would accept to grant us an access to your WordPress website? Kind regards

Mat

micpoh commented 1 year ago

Hello Mat,

I had not heard from you in several weeks. During this time I had a lot of attacks on my website, so I activated and extended the password protection again.

Since the problem has existed for over 3 months now and as it looks at the moment, you have no solution for the problem in the foreseeable future either, I have now decided to replace Matomo with another plugin.

Kind regards Michael

From: mattmary Sent: Tuesday, February 21, 2023 11:32 PM To: matomo-org/matomo-for-wordpress Cc: micpoh ; Mention Subject: Re: [matomo-org/matomo-for-wordpress] Partial data in the WordPress widgets after switching to PHP 8.0/8.1 (Issue #676)

Hello @micpoh

With all the information you provided and after our investigations, we have not been able to reproduce your bug. Just wondering if you would accept to grant us an access to your WordPress website? Kind regards

Mat

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>

mattmary commented 1 year ago

Hello @micpoh

Sorry to see you go, and sorry to have not been able to answer you as soon as you could wish. It is a tricky one indeed but your website security first. Kind regards

Mat

matomo-org / matomo-for-wordpress

Partial data in the WordPress widgets after switching to PHP 8.0/8.1 #676

Endpoints

Crons

Vorgeschriebene Prüfungen

Optionale Prüfungen

Matomo Settings

Logs

WordPress

WordPress Plugins

Server

Database

Browser

2022/12/14 19:28:44 [crit] 9314#9314: *326272 SSL_do_handshake() failed (SSL: error:141CF06C:SSL routines:tls_parse_ctos_key_share:bad key share) while SSL handshaking, client: 134.209.0.0, server: 157.90.0.0:443

Diagnose

System report Troubleshooting

Problembehandlung

Wie können wir helfen?

Beliebte FAQs zur Problembehandlung

Möchtest du einen Fehler melden oder hast du eine Funktionsanforderung?

Bevor du eine Problemmeldung erstellst

Hast du Leistungsprobleme?