Internal Server Error

I found that when I delete .htaccess in /…/node_modules, the Admin menu starts working.

Hello @pumpaxxl

You should leave our .htaccess files as they are required for security and configuration reasons.

If you have 500 errors when opening Matomo, maybe we could try to fix them?

You might have some errors in your PHP error and Apache error logs files. Do you know how to find them?
Could you also share your system report available from the menu Matomo Analytics > Diagnostics?

Kind regards

Mat

Hi, I have it set up on staging site so you can have the admin access. The Matomo diagnostics says this:

# Matomo

* Matomo Plugin Version: 4.11.0
* 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 Version: 4.11.0
* Matomo Blog idSite: 1
* Matomo Install Version: 4.11.0 (Install date: 2022-09-16 21:47:25)
* 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 time: 2022-09-19 07:12:12
* Blog time: 2022-09-19 09:12:12 (Below dates are shown in blog timezone)
* Sync users & sites: Next run: 2022-09-19 21:48:22 (12 hours 36 min) ( Last started: 2022-09-18 21:51:59 (-11 hours 20 min). Last ended: 2022-09-18 21:51:59 (-11 hours 20 min). Interval: daily)
* Archive: Next run: 2022-09-19 09:47:31 (35 min 19s) ( Last started: 2022-09-19 08:48:02 (-24 min 10s). Last ended: 2022-09-19 08:48:17 (-23 min 55s). Interval: hourly)
* Update GeoIP DB: Next run: 2022-10-16 21:48:22 (27 days 12 hours) ( Last started: 2022-09-16 21:48:23 (-2 days 11 hours). Last ended: 2022-09-16 21:48:25 (-2 days 11 hours). 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

* 64-bit PHP Binary: ok 
* Tracker status: ok 
* Memory limit: ok 
* Time zone: ok 
* Open URL: ok 
* PageSpeed is turned off: ok 
* GD > 2.x + FreeType (graphics): ok 
* Other extensions: ok 
* Warning Other functions: warning  (shell_exec It is recommended to turn on this PHP built-in function. <a href='https://matomo.org/faq/troubleshooting/how-to-make-the-diagnostic-managing-processes-via-cli-to-display-ok/' rel='noopener' target='_blank'>Read this to learn more.</a> set_time_limit mail parse_ini_file glob gzopen md5_file )
* Filesystem: ok 
* Last Successful Archiving Completion: ok 
* Database abilities: ok 
* Warning Max Packet Size: warning  (It is recommended to configure a 'max_allowed_packet' size in your MySQL database of at least 64MB. Configured is currently 16MB. )
* Geolocation: ok 
* Update over HTTPS: ok 
* Supports Async Archiving: No
* Location provider ID: geoip2php
* Location provider available: Yes
* Location provider working: Yes
* Warning Proxy header: HTTP_CLIENT_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. Learn more: https://matomo.org/faq/wordpress/how-do-i-fix-the-proxy-header-warning-in-the-matomo-for-wordpress-system-report/)
* Warning Proxy header: HTTP_X_FORWARDED_FOR (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. Learn more: https://matomo.org/faq/wordpress/how-do-i-fix-the-proxy-header-warning-in-the-matomo-for-wordpress-system-report/)
* Had visit in last 5 days: Yes
* Matomo URL: Yes ($site_url/wp-content/plugins/matomo/app)

## Matomo Settings

* Track mode: disabled
* Track codeposition: footer
* Track api endpoint: default
* Track js endpoint: default
* Version history: 4.11.0
* Core version: 4.11.0
* Last tracking settings update: 1663414148
* Last settings update: 1663418423
* Show get started page: 0
* Track ecommerce: No

## Logs

* None: 

# WordPress

* Home URL: $site_url
* Site URL: $site_url
* WordPress Version: 6.0.2
* Number of blogs: 1
* Multisite Enabled: No
* Network Enabled: No
* WP_DEBUG: Yes
* WP_DEBUG_DISPLAY: Yes
* 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: $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: Yes
* 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/09
* Custom upload_path: 
* Custom upload_url_path: 
* Compatible content directory: Yes

# WordPress Plugins

## MU Plugins

* installatron_hide_status_test.php: 

## Plugins

* Antispam Bee: 2.11.1
* Better Search Replace Pro: 1.4 (Network enabled)
* Classic Editor: 1.6.2
* CMP - Coming Soon & Maintenance Plugin: 4.1.2
* Code Snippets: 3.2.0
* Coming Soon Page, Maintenance Mode, Landing Pages & WordPress Website Builder by SeedProd: 6.15.4
* Comments Widget Plus: 1.2.0
* Easy Updates Manager: 9.0.13 (Network enabled)
* Enable Media Replace: 4.0.0
* GDPR Cookie Consent: 2.1.2
* Google Analytics for WordPress by MonsterInsights: 8.8.2
* Header Footer Code Manager Pro: 1.0.4
* Instant Indexing: 1.1.16
* iThemes Security Pro: 7.2.1 (Network enabled)
* Matomo Analytics - Ethical Stats. Powerful Insights.: 4.11.0
* PixelYourSite: 9.2.0
* Rank Math SEO: 1.0.97
* Rank Math SEO PRO: 3.0.12
* ShortPixel Image Optimizer: 5.0.9
* Site Kit by Google: 1.83.0
* SVG Support: 2.5.1
* UpdraftPlus - Backup/Restore: 2.22.14.25
* Videopack (formerly Video Embed & Thumbnail Generator): 4.7.4
* WP-Optimize Premium - Clean, Compress, Cache: 3.2.3
* WP Crontrol: 1.14.0
* WP Fastest Cache: 1.0.5
* WP Mail SMTP: 3.5.2
* WPvivid Backup Plugin: 0.9.77
* WPvivid Plugins Pro: 2.2.9
* Yoast Duplicate Post: 4.5
* Active Plugins: 14 (antispam-bee code-snippets comments-widget-plus duplicate-post enable-media-replace ithemes-security-pro matomo seo-by-rank-math shortpixel-image-optimiser stops-core-theme-and-plugin-updates svg-support video-embed-thumbnail-generator wpvivid-backup-pro wpvivid-backuprestore)
* Theme: Divi (Divi)

# Server

* Server Info: Apache
* PHP OS: Linux
* PHP Version: 8.0.22
* PHP SAPI: fpm-fcgi
* PHP Binary Name: php-fpm
* PHP Error Reporting: 4437 After bootstrap: 4437
* Timezone: UTC
* WP timezone: Europe/Prague
* Locale: en_US
* User Locale: en_US
* Memory Limit: 384M (At least 128MB recommended. Depending on your traffic 256MB or more may be needed.)
* WP Memory Limit: 384M
* WP Max Memory Limit: 384M
* Timezone version: 2022.1
* Time: 1663571532
* Max Execution Time: 180
* Max Post Size: 384M
* Max Upload Size: 402653184
* Max Input Vars: 10000
* Disabled PHP functions: Yes (apache_child_terminate,apache_setenv,define_syslog_variables,diskfreespace,disk_free_space,disk_total_space,dl,exec,leak,link,openlog,passthru,pfsockopen,popen,posix_getgrnam,posix_getpgid,posix_getpwuid,posix_getpwnam,posix_getrlimit,posix_initgroups,posix_kill,posix_mkfifo,posix_mknod,posix_setpgid,posix_setsid,posix_setuid,posix_uname,proc_close,proc_get_status,proc_nice,proc_open,proc_terminate,putenv,readlink,register_tick_function,shell_exec,show_source,symlink,syslog,system)
* zlib.output_compression is off: Yes
* Curl Version: 7.29.0, NSS/3.36
* Suhosin installed: No

# Database

* MySQL Version: 10.3.27
* Mysqli Connect: Yes
* Force MySQL over Mysqli: No
* DB Prefix: kpdy_
* DB CHARSET: utf8
* DB COLLATE: 
* SHOW ERRORS: Yes
* SUPPRESS ERRORS: No
* Uses Socket: No
* Uses IPv6: No
* Matomo tables found: 59
* DB tables exist: Yes
* Matomo users found: 1
* Matomo sites found: 1
* Required permissions: OK

# Browser

* Browser:  (Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/105.0.0.0 Safari/537.36)
* Language: cs-cz,cs,en

I have put all the .htaccess back and enabled debug log with this:

define( ‘WP_DEBUG’, true );
define( ‘WP_DEBUG_LOG’, true );
define( ‘MATOMO_DEBUG’, true );

But when I reload the Matomo page, there is no log file in /wp-content/. The Error 500 is too fast I guess in this case.

Thanks a lot, great plugin!!!

Thank you @pumpaxxl

I can’t see anything unusual in your system report.
Would you mind create me access on your staging website for the email [email protected]? I would like to see what is going on.
Kind regards

Mat

Hi Mat, the admin account is ready. You should have received the email.
Regards,
Pavel.

Hi @pumpaxxl

The problem was your addhandler method was disabled.
We solved it by adding

define('MATOMO_DISABLE_ADDHANDLER', true);

in your wp-config.php file.

Don’t forget to remove my account from your WordPress.

Kind regards

Mat