Benoit
(Benoît)
June 4, 2022, 7:17am
1
Hi,
I’ve updated my matomo to the last version and since yesterday all the UI is broken and I got the error
Failed to load resource: the server responded with a status of 403 () https://www.analytics.setlist-app.com/plugins/CoreHome/javascripts/manifest.json
Any idea how to fix it?
Benoit
(Benoît)
June 6, 2022, 6:45am
2
I’ve installed the 4.10.0 manually and re-install the 4.10.1. The issue is still here on Safari (mac), but working fine on Safari on an iPhone. Working fine on a new private navigation on Brave too, think it’s a problem with the cache.
Erik-Jan
(Erik-Jan)
June 11, 2022, 10:07am
3
I have the same issue. Not everywhere, but it does happen when I try the page overlay feature for example.
It seems that this have been fixed on 4.10.1:
opened 09:53AM - 21 May 22 UTC
closed 01:11AM - 25 May 22 UTC
Regression
Since the update to version 4.10 I get banned from my own server. The reason is … that Fail2ban checks the access_logs for HTTP status 403 and bans the corresponding IPs. In my case Matomo causes these 403 messages in access_log. In the html source code I found this line in Matomo:
`<link rel="manifest" href="plugins/CoreHome/javascripts/manifest.json" crossorigin="use-credentials">`
In Browser I get for this
> Forbidden
> You don't have permission to access this resource.
Apparently the browser has no access to the path. This was not a problem in the previous version of Matomo.
I the same folder is this file `plugins/CoreHome/javascripts/noreferrer.js` and here I can access this file without 403.
So I take a look and found `plugins/htaccess` and here is **json** for "safe static files" missing:
```
# Allow to serve static files which are safe
<Files ~ "\.(gif|ico|jpg|png|svg|js|css|htm|html|mp3|mp4|wav|ogg|avi|ttf|eot|woff|woff2)$">
```
**SOLUTION:** After add "json" here, the issue is gone and manifest.json send HTTP Status 200.
EDIT:
Why you have here "mp3|mp4|wav|ogg|avi", in which cases you use this types of media-files here in matomo?
Its make more sense to add image type "webp" here, if you want to use the modern image format instead of "jpg" in the future. :)
@Benoit , if you still encounter some problem under 4.10.1, please add a comment in this GitHub issue.