Happy Tuesday everyone! Anybody is having issues with the Intercom service related to CORS? After updating google chrome to the latest version (Version 91.0.4472.101 (Official Build) (x86_64)) I'm seeing this persisting. | Community
Skip to main content
Answered

Happy Tuesday everyone! Anybody is having issues with the Intercom service related to CORS? After updating google chrome to the latest version (Version 91.0.4472.101 (Official Build) (x86_64)) I'm seeing this persisting.

  • June 15, 2021
  • 3 replies
  • 747 views
U

Example Error: Access to XMLHttpRequest at 'https://api-iam.intercom.io/messenger/web/ping' from origin 'https://not-my-real-domain.com#39; has been blocked by CORS policy: 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'. The credentials mode of requests initiated by the XMLHttpRequest is controlled by the withCredentials attribute.

Best answer by Eric Fitz

Hey @munish​, CSP settings are typically managed by your system administrator on your end. This isn't something that you update within your Intercom workspace.

3 replies

Eric Fitz
Employee
Forum|alt.badge.img+5
  • Eric FitzEmployee
  • Employee
  • 1630 replies
  • June 17, 2021

Hey @user1165​! Just wanted to make sure that you've followed these instructions in full for setting up Intercom to work with CSP and CORS?

M
  • Munish
  • New Participant
  • 1 reply
  • January 3, 2022

@user1165​ 

I am having the same issue, did you sort it out?

 

@eric f11​  thank you for posting solution - but how and where do I enable CSP settings?

 

Looking forward to your help, thank you

Eric Fitz
Employee
Forum|alt.badge.img+5
  • Eric FitzEmployee
  • Employee
  • 1630 replies
  • Answer
  • January 4, 2022

Hey @munish​, CSP settings are typically managed by your system administrator on your end. This isn't something that you update within your Intercom workspace.


Terms & ConditionsAccessibility statement