CORS errors happen when a webpage makes a request to a different domain than the one that served the page, and the server responds with an HTTP error because the “Origin” header in the request is not allowed by the server’s CORS configuration.
Example console message:
Access to XMLHttpRequest at 'https://api.userback.io/?postWidget'
from origin 'https://your-website.com' has been blocked by CORS policy:
No 'Access-Control-Allow-Origin' header is present on the requested resource.
Why Is This Happening?
CORS errors can happen for a number of reasons:
Recent Updates: Your website or hosting service might have been updated recently.
Tightened Security: Sometimes, security settings get more strict.
Content Security Policy (CSP): Changes in CSP could affect the loading of fonts or other resources from external sources like Userback.
How to Fix It
To fix the error you'll need to add a CORS header, to your website's settings.
There are two options available:
Allow Any Task:
Add Access-Control-Allow-Headers: *
Allow Specific Feedback:
Add Access-Control-Allow-Headers: screenshot.userback.io
If you do not administer your website or application, this information can be passed onto your developer to fix the issue.
Need More Help?
If you've tried the above steps and still face issues, or if you have more questions, feel free to reach out. We're here to help!