matomo-for-wordpress WP error: "Matomo is not set up yet. File not readable:"

Hi. We've used Piwik/Matomo for years, both the plugin and the hosted version, and never encountered this issue on install. Thanks for a wonderful, and private, visitor tracking plugin.

No visits are being tracked on a new WP site we've developed. I've tried from my phone and from a computer incognito window, logged out of WP. The system logs just show the following over and over:

archive_bootstrap 2020-11-16 15:19:54 Matomo is not set up yet. File not readable: $ABSPATH/wp-content/uploads/matomo/config/config.ini.php => EnvironmentValidator.php:85; EnvironmentValidator.php:65; Environment.php:191; Environment.php:100; Bootstrap.php:74; Bootstrap.php:104; ScheduledTasks.php:193; class-wp-hook.php:285; class-wp-hook.php:311; plugin.php:544; wp-cron.php:138;

archive_bootstrap 2020-11-16 17:28:56 Matomo is not set up yet. File not readable: $ABSPATH/wp-content/uploads/matomo/config/config.ini.php => EnvironmentValidator.php:85; EnvironmentValidator.php:65; Environment.php:191; Environment.php:100; Bootstrap.php:74; Bootstrap.php:104; ScheduledTasks.php:193; class-wp-hook.php:285; class-wp-hook.php:311; plugin.php:544; wp-cron.php:138;

archive_bootstrap 2020-11-16 18:09:09 Matomo is not set up yet. File not readable: $ABSPATH/wp-content/uploads/matomo/config/config.ini.php => EnvironmentValidator.php:85; EnvironmentValidator.php:65; Environment.php:191; Environment.php:100; Bootstrap.php:74; Bootstrap.php:104; ScheduledTasks.php:193; class-wp-hook.php:285; class-wp-hook.php:311; plugin.php:544; wp-cron.php:138;

archive_bootstrap 2020-11-16 19:46:17 Matomo is not set up yet. File not readable: $ABSPATH/wp-content/uploads/matomo/config/config.ini.php => EnvironmentValidator.php:85; EnvironmentValidator.php:65; Environment.php:191; Environment.php:100; Bootstrap.php:74; Bootstrap.php:104; ScheduledTasks.php:193; class-wp-hook.php:285; class-wp-hook.php:311; plugin.php:544; wp-cron.php:138;

archive_bootstrap 2020-11-17 00:01:56 Matomo is not set up yet. File not readable: $ABSPATH/wp-content/uploads/matomo/config/config.ini.php => EnvironmentValidator.php:85; EnvironmentValidator.php:65; Environment.php:191; Environment.php:100; Bootstrap.php:74; Bootstrap.php:104; ScheduledTasks.php:193; class-wp-hook.php:285; class-wp-hook.php:311; plugin.php:544; wp-cron.php:138;

archive_bootstrap	2020-11-16 15:19:54	Matomo is not set up yet. File not readable: $ABSPATH/wp-content/uploads/matomo/config/config.ini.php => EnvironmentValidator.php:85; EnvironmentValidator.php:65; Environment.php:191; Environment.php:100; Bootstrap.php:74; Bootstrap.php:104; ScheduledTasks.php:193; class-wp-hook.php:285; class-wp-hook.php:311; plugin.php:544; wp-cron.php:138;
archive_bootstrap	2020-11-16 17:28:56	Matomo is not set up yet. File not readable: $ABSPATH/wp-content/uploads/matomo/config/config.ini.php => EnvironmentValidator.php:85; EnvironmentValidator.php:65; Environment.php:191; Environment.php:100; Bootstrap.php:74; Bootstrap.php:104; ScheduledTasks.php:193; class-wp-hook.php:285; class-wp-hook.php:311; plugin.php:544; wp-cron.php:138;
archive_bootstrap	2020-11-16 18:09:09	Matomo is not set up yet. File not readable: $ABSPATH/wp-content/uploads/matomo/config/config.ini.php => EnvironmentValidator.php:85; EnvironmentValidator.php:65; Environment.php:191; Environment.php:100; Bootstrap.php:74; Bootstrap.php:104; ScheduledTasks.php:193; class-wp-hook.php:285; class-wp-hook.php:311; plugin.php:544; wp-cron.php:138;
archive_bootstrap	2020-11-16 19:46:17	Matomo is not set up yet. File not readable: $ABSPATH/wp-content/uploads/matomo/config/config.ini.php => EnvironmentValidator.php:85; EnvironmentValidator.php:65; Environment.php:191; Environment.php:100; Bootstrap.php:74; Bootstrap.php:104; ScheduledTasks.php:193; class-wp-hook.php:285; class-wp-hook.php:311; plugin.php:544; wp-cron.php:138;
archive_bootstrap	2020-11-17 00:01:56	Matomo is not set up yet. File not readable: $ABSPATH/wp-content/uploads/matomo/config/config.ini.php => EnvironmentValidator.php:85; EnvironmentValidator.php:65; Environment.php:191; Environment.php:100; Bootstrap.php:74; Bootstrap.php:104; ScheduledTasks.php:193; class-wp-hook.php:285; class-wp-hook.php:311; plugin.php:544; wp-cron.php:138;

Unsure why it's saying Matomo isn't set up yet, when the only thing you have to do to install it on WP is install Matomo for WP. We had WP-Matomo installed also at first, but deleted it upon encountering this error. Still no change.

Can you help us figure this out?

Nov 17 '20 06:11 ExcellentPresence

Sorry about that @ExcellentPresence

Any chance you could manually check on the server or using FTP or something if the file $ABSPATH/wp-content/uploads/matomo/config/config.ini.php exists? (you need to replace $ABSPATH with the path to your WordPress directory).

Could you maybe send us the full output of the system report see https://matomo.org/faq/wordpress/i-have-a-problem-how-do-i-troubleshoot-and-enable-wp_debug/ ?

If the system report includes a row Supports Async Archiving: Yes (under Matomo -> Optional Checks) then you might have to complete step 7 in https://matomo.org/faq/wordpress/matomo-for-wordpress-is-not-showing-any-statistics-not-archiving-how-do-i-fix-it/ which basically says to add define( 'MATOMO_SUPPORT_ASYNC_ARCHIVING', false ); to your wp-config.php

If I had to guess then it seems like your system might support async archiving, but when using PHP on the cli then it is not allowed to read the config file for some reason.

Nov 17 '20 20:11 tsteur

Hi.

Yes, config.ini.php does exist.
Installed code to debug to debug.log. No new errors yet.
Also checked server error log, and saw the below (plus several more rows of duplicate "Fatal Error" lines, from 11/13 to 11/16):

[17-Nov-2020 04:01:56 UTC] PHP Fatal error: Uncaught Matomo is not set up yet. File not readable: $ABSPATH/wp-content/uploads/matomo/config/config.ini.php $ABSPATH/wp-content/plugins/matomo/app/core/Application/Kernel/EnvironmentValidator.php:85 thrown in $ABSPATH/wp-content/plugins/matomo/app/core/Application/Kernel/EnvironmentValidator.php on line 85 [18-Nov-2020 02:51:51 UTC] Matomo: Scheduled tasks archive data [18-Nov-2020 02:52:38 UTC] Matomo: Apply 404 tracking changes. Blog ID: 1

Yes, it says Supports Async Archiving: Yes.

It's actually tracking now, just not my own visits. (I do have Do Not Track in my browsers on laptop and phone, but I thought that was only to deny cookie tracking, not all tracking.) I think this was my mistake; I apologize.

Is there a way to send you the full system log privately, if the above still looks like an issue?

Nov 18 '20 03:11 ExcellentPresence

At the top of the Diagnostics screen, it also says:

There are some issues with your system. Matomo will run, but you might experience some minor problems. See below for more information.

Thanks for your help.

Nov 18 '20 03:11 ExcellentPresence

you can send us privately the report to [email protected] . However, if it's working now this might not actually be needed anymore. I'm happy though to have a look at the shown warnings to see if something needs to be done.

Yes do not track doesn't track you at all in this case.

Nov 18 '20 03:11 tsteur

Hi Thomas.

I do still get some yellow errors. Here is the system log below, as I see that no private info is included.

Thanks so much:

  		  # Matomo
Matomo Plugin Version: 1.3.2

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

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

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

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

Matomo Version: 3.14.0

Matomo Blog idSite: 1

Matomo Install Version: 1.3.2 (Install date: 2020-11-17 00:05:52)

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: 2020-11-18 03:12:33

Blog time: 2020-11-17 23:12:33 (Below dates are shown in blog timezone)

Sync users & sites: Next run: 2020-11-18 18:30:50 (19 hours 18 min) ( Last started: 2020-11-17 18:30:52 (-4 hours 41 min). Last ended: 2020-11-17 18:30:52 (-4 hours 41 min). Interval: daily)

Archive: Next run: 2020-11-17 23:30:50 (18 min 17s) ( Last started: 2020-11-17 22:51:51 (-20 min 42s). Last ended: 2020-11-17 22:51:56 (-20 min 37s). Interval: hourly)

Update GeoIP DB: Next run: 2020-12-17 18:30:50 (29 days 19 hours) ( Last started: 2020-11-17 18:30:52 (-4 hours 41 min). Last ended: 2020-11-17 18:31:00 (-4 hours 41 min). Interval: matomo_monthly)

Mandatory checks

PHP version >= : 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

Directories with write access for Tag Manager: ok

Optional checks

Tracker status: ok

Memory limit: ok

Time zone: ok

Open URL: ok

PageSpeed disabled: ok

GD > 2.x + Freetype (graphics): ok

Other extensions: ok

Other functions: ok

Filesystem: ok

Archive Cron: ok

Last Successful Archiving Completion: ok

Max Packet Size: ok

Geolocation: ok

Update over HTTPS: ok

Writable JavaScript Tracker ("/matomo.js"): ok

Supports Async Archiving: Yes

Location provider ID: geoip2php

Location provider available: Yes

Location provider working: Yes

Had visit in last 5 days: Yes

Matomo Settings

Track mode: default

Track codeposition: footer

Track api endpoint: default

Track js endpoint: default

Version history: 1.3.2

Core version: 3.14.0

Last tracking settings update: 1605590266

Last settings update: 1605590266

Track noscript: Yes

Track content: all

Track search: Yes

Track 404: Yes

Track across alias: Yes

Track user id: email

Delete all data uninstall: No

Logs

Warning archive_bootstrap: 2020-11-16 19:46:17 (Matomo is not set up yet. File not readable: $ABSPATH/wp-content/uploads/matomo/config/config.ini.php => EnvironmentValidator.php:85; EnvironmentValidator.php:65; Environment.php:191; Environment.php:100; Bootstrap.php:74; Bootstrap.php:104; ScheduledTasks.php:193; class-wp-hook.php:285; class-wp-hook.php:311; plugin.php:544; wp-cron.php:138;)

Warning archive_bootstrap: 2020-11-17 00:01:56 (Matomo is not set up yet. File not readable: $ABSPATH/wp-content/uploads/matomo/config/config.ini.php => EnvironmentValidator.php:85; EnvironmentValidator.php:65; Environment.php:191; Environment.php:100; Bootstrap.php:74; Bootstrap.php:104; ScheduledTasks.php:193; class-wp-hook.php:285; class-wp-hook.php:311; plugin.php:544; wp-cron.php:138;)

archive_boot: 2020-11-17 21:30:51 (Matomo error: 8: Undefined index: HTTP_USER_AGENT in $ABSPATH/wp-content/plugins/zapier/zapier.php:174 => bootstrap.php:56; bootstrap.php:85; zapier.php:174; class-wp-hook.php:287; plugin.php:206; user.php:2785; pluggable.php:70; pluggable.php:1028; revslider-front.class.php:283; class-wp-hook.php:287; class-wp-hook.php:311; plugin.php:478; wp-settings.php:409; wp-config.php:77; wp-load.php:37; bootstrap.php:95; console:11;)

archive_boot: 2020-11-17 21:30:54 (Matomo error: 8: Undefined index: HTTP_USER_AGENT in $ABSPATH/wp-content/plugins/zapier/zapier.php:174 => bootstrap.php:56; bootstrap.php:85; zapier.php:174; class-wp-hook.php:287; plugin.php:206; user.php:2785; pluggable.php:70; pluggable.php:1028; revslider-front.class.php:283; class-wp-hook.php:287; class-wp-hook.php:311; plugin.php:478; wp-settings.php:409; wp-config.php:77; wp-load.php:37; bootstrap.php:95; console:11;)

archive_boot: 2020-11-17 21:30:56 (Matomo error: 8: Undefined index: HTTP_USER_AGENT in $ABSPATH/wp-content/plugins/zapier/zapier.php:174 => bootstrap.php:56; bootstrap.php:85; zapier.php:174; class-wp-hook.php:287; plugin.php:206; user.php:2785; pluggable.php:70; pluggable.php:1028; revslider-front.class.php:283; class-wp-hook.php:287; class-wp-hook.php:311; plugin.php:478; wp-settings.php:409; wp-config.php:77; wp-load.php:37; bootstrap.php:95; console:11;)

archive_boot: 2020-11-17 21:30:59 (Matomo error: 8: Undefined index: HTTP_USER_AGENT in $ABSPATH/wp-content/plugins/zapier/zapier.php:174 => bootstrap.php:56; bootstrap.php:85; zapier.php:174; class-wp-hook.php:287; plugin.php:206; user.php:2785; pluggable.php:70; pluggable.php:1028; revslider-front.class.php:283; class-wp-hook.php:287; class-wp-hook.php:311; plugin.php:478; wp-settings.php:409; wp-config.php:77; wp-load.php:37; bootstrap.php:95; console:11;)

WordPress

Home URL: $site_url

Site URL: $site_url

WordPress Version: 5.5.3

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: No

CONCATENATE_SCRIPTS: -

COMPRESS_SCRIPTS: -

COMPRESS_CSS: -

ENFORCE_GZIP: -

WP_LOCAL_DEV: -

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: /%post_id%/%postname%/

Possibly uses symlink: No

Compatible content directory: Yes

WordPress Plugins

Avada Builder: 3.1.1

Avada Core: 5.1.1

Coming Soon wp: 1.6.2

Contact Form 7: 5.3

Feeds for YouTube: 1.2.4

Jetpack by WordPress.com: 9.1

Matomo Analytics - Ethical Stats. Powerful Insights.: 1.3.2

Shield Security: 10.1.2

Slider Revolution: 6.2.23

Stripe For WooCommerce: 3.2.7

User Role Editor: 4.57

WooCommerce: 4.7.0

Zapier for WordPress: 1.0.2

Active Plugins: 11 (coming-soon-wp contact-form-7 feeds-for-youtube fusion-builder fusion-core matomo revslider user-role-editor woo-stripe-payment woocommerce zapier)

Server

Server Info: Apache

PHP OS: Linux

PHP Version: 7.3.24

PHP SAPI: litespeed

PHP Binary Name: lsphp

PHP Found Binary: php -q

Timezone: UTC

WP timezone: -04:00

Locale: en_US

User Locale: en_US

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

WP Memory Limit: 40M

WP Max Memory Limit: 1024M

Timezone version: 0.system

Time: 1605669156

Max Execution Time: 300

Max Post Size: 128M

Max Upload Size: 134217728

Max Input Vars: 10000

Disabled PHP functions: No

zlib.output_compression is off: Yes

Curl Version: 7.73.0, OpenSSL/1.1.1h

Suhosin installed: No

Database

MySQL Version: 5.5.5

Mysqli Connect: Yes

Force MySQL over Mysqli: No

DB Prefix: wp_

DB CHARSET: utf8

DB COLLATE:

SHOW ERRORS: No

SUPPRESS ERRORS: No

Uses Socket: No

Uses IPv6: No

Matomo tables found: 115

Matomo users found: 3

Matomo sites found: 1

Required permissions: OK

Browser

Browser: (Mozilla/5.0 (X11; CrOS x86_64 13421.89.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/86.0.4240.183 Safari/537.36)

Language: en-us,en,es

Nov 18 '20 05:11 ExcellentPresence

That's all good @ExcellentPresence these warnings should disappear in a few days and you can ignore them. I'll close the issue for now but feel free to reach out any time if there's anything happening again and we'll be more than happy to help.

Nov 18 '20 20:11 tsteur

Closing this issue as discussed previously.

Oct 04 '22 21:10 mattmary

matomo-for-wordpress matomo-for-wordpress copied to clipboard

WP error: "Matomo is not set up yet. File not readable:"

Endpoints

Crons

Mandatory checks

Optional checks

Matomo Settings

Logs

WordPress

WordPress Plugins

Server

Database

Browser

matomo-for-wordpress
matomo-for-wordpress copied to clipboard