Cross-Origin Read Blocking (CORB) for DataDog logger

I’m using DataDog to log both frontend and backend. Whilst backend works fine, frontend has stopped working and I do get a CORB warning:

Cross-Origin Read Blocking (CORB) blocked cross-origin response with MIME type application/json. See for more details.

The corresponding code is under the path `imports/startup/client/config/

Is anyone else using DataDog to log and would mind sharing how they have overcome the CORB problem for their frontend code?

Please note that I do have separate apps for frontend and backend. Backend works fine.

Thanks in advance!

Is this your case? (scroll to the bottom)

Hi Paul,

seems to be. Open case since 3 years though and my problems are more like a couple of months I’ve got this message.

My main problem is that I don’t get a single line of frontend log in DataDog. Nothing, zip, nada.

Thought that this is stopping the forward to DataDog.

I have errors that MontiAPM has caught but nothing shows up in DataDog, nor in AWS CloudWatch. So I’m not sure whom to blame for the failure, this is all the work of my former frontend employee. As you can probably tell, I have no freaking clue about the DataDog integration between the frontend code, DataDog’s agent/forwarder and AWS CloudWatch :frowning:

Screenshot 2022-07-05 at 21.40.05

Probably the message you see in Chrome is not related to your issue. I guess you don’t see it in other browsers.
I’d make sure I have the right client for the task ( are you using RUM?).
I also see a recent deprecation for TLS <1.2 and older Agents (I think older than 5) might not work anymore.

I have an Electron app, so can’t change the browser

Yes, it’s the right client as it was working fine before

Ok, that might be a reason why it has stopped or almost stopped (217 lines in 1 month vs 4.36 million lines for the backend in the same period of time).

Thanks Paul - good hints!