Content-Security-Policy-Report-Only from app.hubspot.com is reporting errors to browsers

Developer Support APIs & Integrations
21

it seems to be all good now, thanks!

22

Did this issue get un-fixed? :slightly_smiling_face: 'm getting this error today.

23

Is this happening again?

24

Pls help here? The iframe of hubspot meetings embed is not loading

25

It works now, thank you!

26

We’ve had the same issue and it is causing problems with our google ads becasue the link is being rejected. Since there as been a fix, do we need to update our forms and reload?

27

@EFinnestead , I don’t think there is anything that needs to be done on your end :grinning_face:

28

We are still dealing with this issue. Is there a hard date when this will be fixed @dennisedson?

29

@JCusick , this should be resolved as a fix was deployed. If you are still experiencing issues here, I would recommend contacting support directly.

If you do, please reference this thread in your request

30

It looks like this issue may be back. We get this now on all external sites that use HubSpot forms: Refused to frame ‘https://app.hubspot.com/’ because an ancestor violates the following Content Security Policy directive: “frame-ancestors ‘self’ app.hubspot.com”.

31

FYI, I’m working with David (support) on the issue. Just wanted to see if there were any others getting this. We get an error on all external sites that use the HS forms. No matter what I set locally (running on a laptop for example), this error will not go away. So assuming it’s from the HS website.

32

We are seeing this issue as well.

33

Thank you for the confirmation. I appreciate it. I will let our support person know. The will truly just need to let the downstream apps handle security vs forcing top down…which in this case will not work at all. Thanks again.

34

Echoing what others are saying. We are seeing the same issue again. Seems to be a regression.

35

We are also experiencing the same error in the console. I have read that a fix has been made but wondering if we have to create a new form and redeploy a new script?

Is there any documentation on this issue to help fix? Cheers!

36

Hey all, I am looking into this

37

As an update, the team has discovered the reason this is occurring and is working on a fix

38

I am also seeing this issue.

39

A fix has been deployed. Please feel free to reach out if the issue persists.

Thanks for notifying us!

40

I just redeployed an application reverting the code back to what it was before (no additional updates). All looks to be working fine. Please inform developers to “not” deploy script/security changes unless they run things through a test bed. This caused quite a bit of havoc. Thanks.