Dreaded Oops... there was a problem

[HelsinkiSisu]

One of my Matomo installs is consistently throwing up “Oops… there was a problem during the request. Maybe the server had a temporary issue, or maybe you requested a report with too much data. Please try again. If this error occurs repeatedly please contact your Matomo administrator for assistance.”

It occurs only when accessing site dashboards (two sites). All hits are updated and visible via the specific metrics. Just not in the dashboard view (which is used most). These are both low volume sites but auto archiving is setup and working fine (according to the log). There is no error log.

Suggestions gratefully received.

Here’s the latest archive log…

INFO [2022-03-26 17:05:01] 16049  ---------------------------
INFO [2022-03-26 17:05:01] 16049  INIT
INFO [2022-03-26 17:05:01] 16049  Running Matomo 4.8.0 as Super User
INFO [2022-03-26 17:05:01] 16049  ---------------------------
INFO [2022-03-26 17:05:01] 16049  NOTES
INFO [2022-03-26 17:05:01] 16049  - Async process archiving supported, using CliMulti.
INFO [2022-03-26 17:05:01] 16049  - Reports for today will be processed at most every 900 seconds. You can change this value in Matomo UI > Settings > General Settings.
INFO [2022-03-26 17:05:01] 16049  - Archiving was last executed without error 59 min 52s ago.
INFO [2022-03-26 17:05:01] 16049  ---------------------------
INFO [2022-03-26 17:05:01] 16049  START
INFO [2022-03-26 17:05:01] 16049  Starting Matomo reports archiving...
INFO [2022-03-26 17:05:01] 16049  Start processing archives for site 1.
INFO [2022-03-26 17:05:01] 16049    Will invalidate archived reports for today in site ID = 1's timezone (2022-03-26 00:00:00).
INFO [2022-03-26 17:05:01] 16049    Will invalidate archived reports for yesterday in site ID = 1's timezone (2022-03-25 00:00:00).
INFO [2022-03-26 17:05:02] 16049  Archived website id 1, period = day, date = 2022-03-26, segment = '', 11 visits found. Time elapsed: 0.847s
INFO [2022-03-26 17:05:03] 16049  Archived website id 1, period = week, date = 2022-03-21, segment = '', 87 visits found. Time elapsed: 1.298s
INFO [2022-03-26 17:05:05] 16049  Archived website id 1, period = month, date = 2022-03-01, segment = '', 298 visits found. Time elapsed: 1.554s
INFO [2022-03-26 17:05:06] 16049  Archived website id 1, period = year, date = 2022-01-01, segment = '', 1132 visits found. Time elapsed: 1.206s
INFO [2022-03-26 17:05:06] 16049  Finished archiving for site 1, 4 API requests, Time elapsed: 5.080s [1 / 4 done]
INFO [2022-03-26 17:05:06] 16049  Start processing archives for site 2.
INFO [2022-03-26 17:05:06] 16049    Will invalidate archived reports for yesterday in site ID = 2's timezone (2022-03-25 00:00:00).
INFO [2022-03-26 17:05:06] 16049  Finished archiving for site 2, 0 API requests, Time elapsed: 0.011s [2 / 4 done]
INFO [2022-03-26 17:05:06] 16049  Start processing archives for site 3.
INFO [2022-03-26 17:05:06] 16049  Finished archiving for site 3, 0 API requests, Time elapsed: 0.005s [3 / 4 done]
INFO [2022-03-26 17:05:06] 16049  Start processing archives for site 4.
INFO [2022-03-26 17:05:06] 16049  Finished archiving for site 4, 0 API requests, Time elapsed: 0.004s [4 / 4 done]
INFO [2022-03-26 17:05:06] 16049  Done archiving!
INFO [2022-03-26 17:05:06] 16049  ---------------------------
INFO [2022-03-26 17:05:06] 16049  SUMMARY
INFO [2022-03-26 17:05:06] 16049  Processed 4 archives.
INFO [2022-03-26 17:05:06] 16049  Total API requests: 4
INFO [2022-03-26 17:05:06] 16049  done: 4 req, 5178 ms, no error
INFO [2022-03-26 17:05:06] 16049  Time elapsed: 5.178s
INFO [2022-03-26 17:05:06] 16049  ---------------------------
INFO [2022-03-26 17:05:06] 16049  SCHEDULED TASKS
INFO [2022-03-26 17:05:06] 16049  Starting Scheduled tasks... 
INFO [2022-03-26 17:05:06] 16049  Scheduler: executing task Piwik\Plugins\CustomJsTracker\Tasks.updateTracker...
INFO [2022-03-26 17:05:06] 16049  Scheduler: finished. Time elapsed: 0.015s
INFO [2022-03-26 17:05:06] 16049  Scheduler: executing task Piwik\Plugins\PrivacyManager\Tasks.deleteLogData...
INFO [2022-03-26 17:05:06] 16049  Scheduler: finished. Time elapsed: 0.000s
INFO [2022-03-26 17:05:06] 16049  Scheduler: executing task Piwik\Plugins\PrivacyManager\Tasks.anonymizePastData...
INFO [2022-03-26 17:05:06] 16049  Scheduler: finished. Time elapsed: 0.001s
INFO [2022-03-26 17:05:06] 16049  done
INFO [2022-03-26 17:05:06] 16049  ---------------------------

[schelli]

have you checked this?

After update to 4.8: Oops... there was a problem during the request

After I updated Matomo today I get the “Oops… there was a problem during the request…” error on nearly every widget on the dashboard as well on the every report page. Auto-archiving is active and there are no errors in PHP error logs. It just started this morning when I updated Matomo via the UI. It was a little bit strange as as was pointed back to the dashboard directly without any upgrade - maybe there was something wrong during the update process?

In my case I just deleted the folder templates_c and the errors where gone.

[HelsinkiSisu]

Thanks! I checked and noticed root permissions instead of www-data on some of the folders in templates_c. I renamed templates_c and the problem did indeed disappear and the folder and structure was rebuilt at the next archive.

[HelsinkiSisu]

Actually, the same happened on another site and doing a recursive www-data chown on templates_c fixed it.