Hey All,
I'm seeing this error. I found this <ar...
# gooddata-clouds
Steve Fox
03/16/2026, 9:00 PMHey All,
I'm seeing this error. I found this article. Can someone point me to what our default CSP.
Copy code
Access to resource at '<https://collector.iad1.prodgdc.com/v1/traces>' from origin '<https://analytics.golmn.com>' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: The value of the 'Access-Control-Allow-Origin' header in the response must not be the wildcard '*' when the request's credentials mode is 'include'.Understand this errork
kapa.ai
03/16/2026, 9:00 PMNew message text here
s
Steve Fox
03/16/2026, 9:06 PMOk, fine but its saying :
Access to resource at 'https://collector.iad1.prodgdc.com/v1/traces' from origin 'https://analytics.golmn.com' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: The value of the 'Access-Control-Allow-Origin' header in the response must not be the wildcard '*' when the request's credentials mode is 'include'.
What is collector.iad1.prodgdc.com/v1/traces. is that a gooddata service? If yes, I'm assuming I should inclue in my CORS for my environment?
This appear as soon as I open a gooddata workspace in the Gooddata ui.
Steve Fox
03/16/2026, 9:09 PMiad1.prodgdc looks to be the IAD1 Data Center and the domain prodgdc.com is good data production.
So am I supposed to enable this domain? What does it do?
j
Julius Kos
03/16/2026, 9:17 PMHi Steve, I believe there's no action needed and it shouldn't affect GoodData's functionality. I can see same error in console log in my internal domain.
However, let me ask internally what is triggering this. We will get back to you.
s
Steve Fox
03/16/2026, 9:22 PMI would bet its analytics?
• Or something that should have been updated to use my domain instead of the data center's domain.
Thank you
f
Francisco Antunes
03/17/2026, 4:35 PMHi Steve, we are checking this internally with our frontend engineers - but it’s not something you need to worry about.
The error message probably relates to some of our telemetry collectors and should have no impact on your end. We’ll find out what’s going on and update you when we learn more!
s
Steve Fox
03/18/2026, 12:58 PMOk, thank you.
We track errors in the console quite a bit with datadog, so these things come up quite a bit when they're out of the norm. We get enough tiger backend errors as it is, so this on top just adds confusion to our developers.
f
Francisco Antunes
03/24/2026, 10:15 AMHi @Steve Fox, sorry for the delay here. Our engineers have checked this and have confirmed that this particular CORS error message is not actionable nor indicative of any issues and can be safely ignored.
They are working on ensuring that it will no longer be displayed. Thank you for reporting this!
Francisco Antunes
03/26/2026, 9:06 AMHi @Steve Fox - good news! Our devs managed to resolve the issue, and we are no longer seeing these CORS errors on the console. Thanks again for the report 🙂
s
Steve Fox
03/26/2026, 4:23 PMExcellent! Thank you
Steve Fox
03/26/2026, 4:26 PM@Francisco Antunes I confirmed I'm no longer getting the above, but I am concerned while in gooddata ui that I'm getting this in the console:
Looks like there is a race condition? I've seen in our other thread that featurehub is related to controlling beta flagged feature controls
Steve Fox
03/26/2026, 4:26 PMSome of these default to true -> which has led to unintended UI issues.
Steve Fox
03/26/2026, 4:27 PMLuckily our teams do not use the gooddata UI directly for our customers, but worth noting that if an error for featurehub is found -> the defaults do not always resemble a "non-beta" experience.
f
Francisco Antunes
03/27/2026, 10:00 AMHi Steve, thank you for the reply. I checked on our side, and we already have another ticket from your Org discussing this issue. I can see you are CC’d there too.
I’ve added your comments there and our team is currently investigating it. We will update your team about this issue through there. Thank you!
4 Views