For some reason, the configuration for cross domain requests has no effect. If you follow the official documentation, it should be straight forward. In Yunohost, the configuration is indeed written to the config file but you have also to manually modify the NGINX configuration by adding a more_set_headers "Access-Control-Allow-Origin: *"; directive (not that secure, I know, it’s just an example). For some applications (such as the one I’m trying to package), CORS is the way Matomo can retrieve informations about visitors. Can the NGINX configuration be modified accordingly?
This is an old thread, but still relevant. I'd love to know this too. I have a couple of other apps that I'm having CORS issues with. Indeed, no luck with following the official road to set it up.
For some reason, the configuration for cross domain requests has no effect. If you follow the official documentation, it should be straight forward. In Yunohost, the configuration is indeed written to the config file but you have also to manually modify the NGINX configuration by adding a
more_set_headers "Access-Control-Allow-Origin: *";
directive (not that secure, I know, it’s just an example). For some applications (such as the one I’m trying to package), CORS is the way Matomo can retrieve informations about visitors. Can the NGINX configuration be modified accordingly?