-
Notifications
You must be signed in to change notification settings - Fork 342
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error private directories are accessible #304
Comments
Same problem here - as we are not using any volume mounts, the image should take care of the permissions. |
Duplicate of #262 |
@J0WI Thank you for the link. However, we were aware of this "How to" and as I wrote in my initial comment, this documentation is not very helpful. As we do not have the possibility to make this adjustments on our web server because our Web App Container is not persistent. Nevertheless, seems like this issue of private directories was fixed now directly by Matomo (error message is not showing on our side anymore). |
Hello.
We have installed Matomo latest (4.13.3) in an Azure Web App Container - Image from Docker Hub.
We are getting error messages similar to the one in the screenshot regarding different directories.
The How to fix from Matomo is not really helpful in this case as we have also no write permissions on our Web App Container.
How can we fix this?
We believe this directories should be protected automatically by Matomo.
Thanks in advance.
The text was updated successfully, but these errors were encountered: