Unable to reinstall after crash

I’m having the exact same issue and error (Proxy Error The proxy server received an invalid response from an upstream server. The proxy server could not handle the request Reason: Error reading from remote server matomo)

After the update, Matomo keeps loading when I try to open the Summary or any other Matomo option from the WordPress dashboard and then after a while I get the proxy error .

This seems to be a bug introduced in 4.13.4.

For the time being I’ve resolved this by rolling back to 4.13.3 from here https://www.ads-software.com/plugins/matomo/advanced/ But that’s on your own risk.

Hope this helps for the time being and hopefully the dev team will look into this and join this thread.

@schaipau Can you please share us the system check so we can investigate on this further? Please follow this guide How do I find and copy the system report in Matomo for WordPress?

@emermatomo I have changed the wp-config.php file

# Errors

* Error PHP cli Version:? (Your PHP cli version is not compatible with the <a  target="_blank">Matomo requirements</a>. Please upgrade your PHP cli version, otherwise, you might have some archiving errors)

* Error MySQLi support: missing (Your PHP cli does not load the MySQLi extension. You might have archiving problems in Matomo but also others problems in your WordPress cron tasks. You should enable this extension)

# Matomo

* Matomo Plugin Version: 4.13.5

* Config exists and is writable.: Yes ("$abs_path/wp-content/uploads/matomo/config/config.ini.php" )

* JS Tracker exists and is writable.: Yes ("$abs_path/wp-content/uploads/matomo/matomo.js" )

* Plugin directories: Yes ([{"pluginsPathAbsolute":"$abs_path\/wp-content\/plugins\/matomo\/plugins","webrootDirRelativeToMatomo":"..\/"}])

* Tmp directory writable: Yes ($abs_path/wp-content/cache/matomo)

* Matomo Blog idSite: 1

* Matomo Install Version: 4.13.4 (Install date: 2023-02-26 20:20:13)

## 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 time: 2023-03-02 20:04:52

* Blog time: 2023-03-02 21:04:52 (Below dates are shown in blog timezone)

* Sync users & sites: Next run: 2023-03-03 08:57:58 ( Last started: 2023-03-02 13:35:35. Last ended: 2023-03-02 13:35:35. Interval: daily)

* Archive: Next run: 2023-03-02 21:57:58 ( Last started: 2023-03-02 20:58:24. Last ended: 2023-03-02 20:58:40. Interval: hourly)

* Update GeoIP DB: Next run: 2023-03-31 09:57:58 ( Last started: 2023-03-01 08:58:23. Last ended: 2023-03-01 08:58:26. Interval: matomo_monthly)

## Matomo Settings

* Track mode: disabled

* Track codeposition: footer

* Track api endpoint: default

* Track js endpoint: default

* Version history: 4.13.5, 4.13.4

* Core version: 4.13.3

* Last tracking settings update: 1677439700

* Last settings update: 1677439700

## Logs

* None:?

# 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: Yes

* WP_DEBUG_LOG: No

* DISABLE_WP_CRON: -

* FORCE_SSL_ADMIN: Yes

* WP_CACHE: Yes

* 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: Yes

* 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

* Custom upload_path: $abs_path/wp-content/uploads

* Custom upload_url_path:?

* Compatible content directory: Yes

# WordPress Plugins

* Burst Statistics - Privacy-Friendly Analytics for WordPress: 1.3.4

* Complianz | GDPR/CCPA Cookie Consent: 6.4.2

* Kadence Blocks – Gutenberg Blocks for Page Builder Features: 3.0.20

* Limit Login Attempts Reloaded: 2.25.13

* Maintenance: 4.07

* Matomo Analytics - Ethical Stats. Powerful Insights.: 4.13.5

* Rank Math SEO: 1.0.109

* Smash Balloon Instagram Feed: 6.1.2

* W3 Total Cache: 2.3.0 (Network enabled)

* WP Google Map: 1.9.0

* Active Plugins: 10 (burst-statistics complianz-gdpr gmap-embed instagram-feed kadence-blocks limit-login-attempts-reloaded maintenance matomo seo-by-rank-math w3-total-cache)

* Theme: kadence (kadence)

# Server

* Server Info: Apache/2.4.54 (Unix)

* Apache AddHandler support: Supported

* PHP OS: Linux

* PHP Version: 8.0.27

* PHP SAPI: cgi-fcgi

* PHP Binary Name: /opt/RZphp80/bin/php

* PHP Maxmind DB extension: Not loaded

* PHP Error Reporting:? After bootstrap: 4437

* Timezone: UTC

* WP timezone: Europe/Amsterdam

* Locale: nl_NL

* User Locale: nl_NL

* Memory Limit: 512M (At least 128MB recommended. Depending on your traffic 256MB or more may be needed.)

* WP Memory Limit: 40M

* WP Max Memory Limit: 512M

* Timezone version: 2022.6

* Time: 1677787494

* Max Execution Time: 240

* Max Post Size: 128M

* Max Upload Size: 134217728

* Max Input Vars: 4000

* Disabled PHP functions: No

* zlib.output_compression is off: Yes

* Curl Version: 7.86.0, OpenSSL/1.1.1q

* Suhosin installed: No

# PHP cli

* Error PHP cli Version:? (Your PHP cli version is not compatible with the <a  target="_blank">Matomo requirements</a>. Please upgrade your PHP cli version, otherwise, you might have some archiving errors)

* Error MySQLi support: missing (Your PHP cli does not load the MySQLi extension. You might have archiving problems in Matomo but also others problems in your WordPress cron tasks. You should enable this extension)

# Database

* MySQL Version: 5.7.38

* Mysqli Connect: Yes

* Force MySQL over Mysqli: No

* DB Prefix: nmfs_

* DB CHARSET: utf8

* DB COLLATE:?

* SHOW ERRORS: No

* SUPPRESS ERRORS: No

* Uses Socket: No

* Uses IPv6: No

* Matomo tables found: 43

* DB tables exist: Yes

* Matomo users found: 2

* Matomo sites found: 1

* Required permissions: OK

# Browser

* Browser:? (Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/16.3 Safari/605.1.15)

@schaipau was the issue fixed after changing the wp-config.php file? If not that doesn’t fix the issue, can you please switch the php version to 7.* or 8.1.

@emermatomo it looks like it is working. I can access the menu items under Matomo. However there is still the message “There are some errors in the?Matomo Diagnostics System report?that may prevent the plugin for working normally.” I will try if it works normally or after using php 8.1 tomorrow. Thanks for your support so far.

Thanks for letting me know. Please don’t hesitate to update this thread if you’re still having issues.

@emermatomo I am reluctant to switch to php 8.1 because other plugin’s might cause problems. My current PHP version 8.027 meets the Matomo requirements according the website. I have downgraded matomo version to 4.13.3. Although the diagnostics is not opening (I have removed matomo save mode in wp-config), the other options do. Are there any new insights for this problem.

Hi @schaipau Sorry for the late response. If it’s working, there is no need to switch your php version. The errors you have in php log files are “normal”. It will disappear in the next published release.

@emermatomo. I have updated to the latest version. It did not resolve my problem. I now get an E_ERROR. I had no access anymore to my WordPress site. After fixing this. Non of the Matomo menu items work. WordPress shows a critical error page. I can’t make a system report. Even with the matomo save mode line in WP-config file.

@schaipau?I just saw your response on the other thread and replied to it. Is it possible to ask your hosting provider to back up your site first before updating the php version? If it caused an issue after updating it, you can simply revert it using the backup.

Hi @schaipau I assume that it worked since it’s been 2 weeks and will therefore mark the issue for now as resolved. If something is not working feel free to leave a comment and we continue following up.

@emermatomo. After some months I have just installed php 8.1 and updated Matomo v13 to the latest version. Unfortunately the problem still exists.
This is the error thrown in WordPress plugin page:
Een fout van het type E_ERROR werd veroorzaakt op regelnummer 996 van het bestand /mnt/web203/d1/27/511705827/htdocs/STRATO-apps/wordpress_01/app/wp-content/plugins/matomo/classes/WpMatomo/Admin/SystemReport.php. Foutmelding: Uncaught Error: Class "Piwik\Plugins\SitesManager\Model" not found in /mnt/web203/d1/27/511705827/htdocs/STRATO-apps/wordpress_01/app/wp-content/plugins/matomo/classes/WpMatomo/Admin/SystemReport.php:996 Stack trace: #0 /mnt/web203/d1/27/511705827/htdocs/STRATO-apps/wordpress_01/app/wp-content/plugins/matomo/classes/WpMatomo/Admin/SystemReport.php(254): WpMatomo\Admin\SystemReport->get_wordpress_info() #1 /mnt/web203/d1/27/511705827/htdocs/STRATO-apps/wordpress_01/app/wp-content/plugins/matomo/classes/WpMatomo/Admin/SystemReport.php(290): WpMatomo\Admin\SystemReport->get_error_tables() #2 /mnt/web203/d1/27/511705827/htdocs/STRATO-apps/wordpress_01/app/wp-content/plugins/matomo/classes/WpMatomo/Admin/Menu.php(183): WpMatomo\Admin\SystemReport->errors_present() #3 /mnt/web203/d1/27/511705827/htdocs/STRATO-apps/wordpress_01/app/wp-includes/class-wp-hook.php(308): WpMatomo\Admin\Menu->add_menu() #4 /mnt/web203/d1/27/511705827/htdocs/STRATO-apps/wordpress_01/app/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters() #5 /mnt/web203/d1/27/511705827/htdocs/STRATO-apps/wordpress_01/app/wp-includes/plugin.php(517): WP_Hook->do_action() #6 /mnt/web203/d1/27/511705827/htdocs/STRATO-apps/wordpress_01/app/wp-admin/includes/menu.php(155): do_action() #7 /mnt/web203/d1/27/511705827/htdocs/STRATO-apps/wordpress_01/app/wp-admin/menu.php(420): require_once('...') #8 /mnt/web203/d1/27/511705827/htdocs/STRATO-apps/wordpress_01/app/wp-admin/admin.php(158): require('...') #9 {main} thrown

WordPress versie 6.2.2
Actief thema: Kadence (versie 1.1.41)
Huidige plugin: Matomo Analytics – Ethical Stats. Powerful Insights. (versie 4.15.0)
PHP versie 8.1.21

Any thoughts what can be done to fix this error?

• This reply was modified 1 year, 6 months ago by schaipau.

I have downgraded now again to 4.13.3
with MATOMO_SAFE_MODE = true

With this version I can still use Matomo functionality without WordPress error message.
But still with the PHP Cli Version compatibility error “Your PHP cli version is not compatible with the %s. Please upgrade your PHP cli version, otherwise, you might have some archiving errors” and MSQLi load error. “Your PHP cli does not load the MySQLi extension. You might have archiving problems in Matomo but also others problems in your WordPress cron tasks. You should enable this extension.”
According to my phpinfo.php file the extension is loaded.

@schaipau Thank you for keeping us updated. To fix the php cli version error, could you please follow the troubleshooting steps on this guide: https://matomo.org/faq/how-to-solve-the-error-message-your-php-cli-version-is-not-compatible-with-the-matomo-requirements/

I hope that helps. Please let us know how it goes.

@emermatomo. I have checked my PHP 8.1.21 – phpinfo.ini file and found “Configuration File (php.ini) Path” = /opt/RZphp81/etc. Assuming that the location of the php.ini file is the CLI path. After adding php_binary_path=”/opt/RZphp81/etc” in the config.ini.php file and flushing the cache, it was still not working. So I am not 100% sure if the CLI path is right. Do you have any knowledge about the phpinfo file and if it contains the CLI path?