After update: Oops… there was a problem during the request

After upgrading to 4.6.1 I get this error message:

System health check is 100 % fine and archiving is done by cron without any issues. This is the latest log (5 minutes ago):

INFO [2021-12-01 10:42:12] 2516428 ---------------------------
INFO [2021-12-01 10:42:12] 2516428 INIT
INFO [2021-12-01 10:42:12] 2516428 Running Matomo 4.6.1 as Super User
INFO [2021-12-01 10:42:12] 2516428 ---------------------------
INFO [2021-12-01 10:42:12] 2516428 NOTES
INFO [2021-12-01 10:42:12] 2516428 - Async process archiving supported, using CliMulti.
INFO [2021-12-01 10:42:12] 2516428 - Reports for today will be processed at most every 60 seconds. You can change this value in Matomo UI > Settings > General Settings.
INFO [2021-12-01 10:42:12] 2516428 - Archiving was last executed without error 1 min 36s ago
INFO [2021-12-01 10:42:12] 2516428 ---------------------------
INFO [2021-12-01 10:42:12] 2516428 START
INFO [2021-12-01 10:42:12] 2516428 Starting Matomo reports archiving…
INFO [2021-12-01 10:42:12] 2516428 Start processing archives for site 1.
INFO [2021-12-01 10:42:12] 2516428 Will invalidate archived reports for today in site ID = 1’s timezone (2021-12-01 00:00:00).
INFO [2021-12-01 10:42:12] 2516428 Will invalidate archived reports for yesterday in site ID = 1’s timezone (2021-11-30 00:00:00).
INFO [2021-12-01 10:42:12] 2516428 Archived website id 1, period = day, date = 2021-12-01, segment = ‘’, 467 visits found. Time elapsed: 0.629s
INFO [2021-12-01 10:42:13] 2516428 Archived website id 1, period = month, date = 2021-12-01, segment = ‘’, 467 visits found. Time elapsed: 0.607s
INFO [2021-12-01 10:42:14] 2516428 Archived website id 1, period = week, date = 2021-11-29, segment = ‘’, 4120 visits found. Time elapsed: 1.320s
INFO [2021-12-01 10:42:36] 2516428 Archived website id 1, period = year, date = 2021-01-01, segment = ‘’, 682598 visits found. Time elapsed: 21.770s
INFO [2021-12-01 10:42:36] 2516428 Finished archiving for site 1, 4 API requests, Time elapsed: 24.449s [1 / 1 done]
INFO [2021-12-01 10:42:36] 2516428 Done archiving!
INFO [2021-12-01 10:42:36] 2516428 ---------------------------
INFO [2021-12-01 10:42:36] 2516428 SUMMARY
INFO [2021-12-01 10:42:36] 2516428 Processed 4 archives.
INFO [2021-12-01 10:42:36] 2516428 Total API requests: 4
INFO [2021-12-01 10:42:36] 2516428 done: 4 req, 24476 ms, no error
INFO [2021-12-01 10:42:36] 2516428 Time elapsed: 24.476s
INFO [2021-12-01 10:42:36] 2516428 ---------------------------
INFO [2021-12-01 10:42:36] 2516428 SCHEDULED TASKS
INFO [2021-12-01 10:42:36] 2516428 Starting Scheduled tasks…
INFO [2021-12-01 10:42:36] 2516428 done
INFO [2021-12-01 10:42:36] 2516428 ---------------------------

The “Oops” error appears on several pages in the backend, e. g. here as well:

I already tried to increase php memory limit (to -1) and execution time from 30 to 300, but without success. The really strange thing is that I can’t find any error message in any logs, it’s only the “Oops” message in the backend.

Any ideas what I can do to find the real cause? Until I updated to 4.6.0 yesterday, everything was fine. Today I updated again to 4.6.1 but the error is still there.

Finally found the solution: Giving more rights to matomo-dir/tmp did the trick. I don’t know why this didn’t show up in the system check, but an Error 500 in the Firefox network log when loading the dashboard gave me the idea.

1 Like