matomo-org / matomo-org/matomo-nodejs-tracker
CORS problem with this module and cloud version
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 117
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
Hi there!
We're trying the beta of your cloud version;
Our innocraft url is: apartum.innocraft.cloud
We're using matomo-tracker
And the problem is that each request to Matomo servers return with this error:
No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'xxxx' is therefore not allowed access. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.
Sessions looks like are being tracked, but we're afraid of possible colateral problems due to this error.
How can we change this?
I've read this: https://matomo.org/faq/how-to/faq_18694/
But as this is a cloud version, we don't have any access to config.ini.php
Any help please?
Thanks in advance!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported browser request from the matomo-tracker module against the Matomo cloud endpoint and compare it with the CORS guidance linked in the issue. Check whether the repository controls the request behavior or whether the missing header must be changed by the cloud service; done means requests complete without the reported CORS error or the issue is documented as externally owned.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100