Matomo 'Oops... There Was a Problem During the Request' Error

How to fix it

Try these in order — the most common fix is first.

1. 1. Find the real error

   Copy steps
   1. Open F12 > Network, click the failed request and note the status code
   2. Check the Console for JavaScript errors
   Did this fix it? Yes No

2. 2. Set up cron archiving

   1. Run core:archive by cron and disable archiving from the browser in General Settings (Matomo's most common fix)
   Did this fix it? Yes No

3. 3. Clear caches and check permissions

   Copy steps
   1. Hard refresh, test in a private window and run ./console cache:clear
   2. Make sure tmp/ and config/ are writable by the web server user
   Did this fix it? Yes No

4. 4. Read the logs

   1. Check tmp/logs/matomo.log and your Apache or nginx error log (for example /var/log/nginx/error.log)
   Did this fix it? Yes No

5. 5. Raise PHP limits and isolate plugins

   Copy steps
   1. Increase memory_limit and max_execution_time in the correct php.ini and restart PHP-FPM
   2. Run ./console plugin:deactivate --all then reactivate one at a time
   Did this fix it? Yes No

6. 6. Fix CORS or CSRF

   Copy steps
   1. Set enable_cors = 1 under [General] if Matomo is on another domain
   2. Add trusted_hosts[] = "your-matomo-url.com" and enable_framed_pages = 1 when embedded
   Did this fix it? Yes No

7. 7. Verify the install

   Copy steps
   1. Run ./console diagnostics:run
   2. Re-extract the latest release over the install if files are missing and reapply permissions
   Did this fix it? Yes No

Symptoms

Reports show 'Oops... there was a problem during the request. Maybe the server had a temporary issue or you requested a report with too much data.'

Why it happens

• Browser archiving overloading the server on large reports
• 403 from file permissions, ModSecurity or .htaccess/nginx rules
• 500 from PHP errors or low memory, 502/504 from PHP-FPM problems
• CORS or CSRF issues when Matomo is on a different domain
• Ad blockers blocking the request (net::ERR_BLOCKED_BY_CLIENT)
• Plugin conflicts or incomplete files after an update

This guide also covers

• matomo oops there was a problem during the request
• matomo oops error
• matomo report too much data

The same problem in other apps

All not loading, error messages & connection guides →

• Umami Migration Failed (Prisma P3009 / P3018 Error) (Umami)
• PostHog Toolbar or Heatmaps Not Loading (PostHog)

Other Matomo errors

• Matomo Shows No Data (There Is No Data for This Report)
• Matomo Reports Not Updating (Archiving Cron Not Working)
• Matomo for WordPress Not Showing Statistics
• Matomo Archiving Slow or Out of Memory on Large Sites
• Matomo Blocked by Ad Blockers (Undercounting Visitors)
• Why Matomo Numbers Differ From Google Analytics and Search Console
• How to Exclude Your Own Visits in Matomo
• Matomo 'Keyword Not Defined' (Missing Search Keywords)