Join Discord
Powered by
GHL MCP Integration OAuth Failure - Critical CORS ...
# support
m
M.Khatib
12/19/2025, 1:03 PM
Hi Vapi Support Team, I'm following up on my previous ticket regarding the GoHighLevel (GHL) integration failure. After investigating with browser developer tools, I've identified several critical technical issues preventing the OAuth flow from completing: Issues Identified: CORS Blocking (Primary Issue) Multiple requests are being blocked by Cross-Origin Resource Blocking The OAuth callback from GHL cannot complete due to CORS policy restrictions This prevents the integration from finalizing after user authorization Content Security Policy Violations CSP is blocking script-src directive (status: blocked) Evaluation of JavaScript strings is being prevented These restrictions are interfering with the OAuth authentication flow API Communication Failures Repeated net::ERR_QUIC_PROTOCOL_ERROR 200 (OK) errors on
https://api.vapi.ai/events
These errors occur during the integration process Suggests backend communication issues during OAuth callback Current Behavior: Click "Connect" → Opens GHL permissions page ✓ Accept permissions ✓ Choose subaccount ✓ Redirect back to Vapi → Integration shows as NOT connected ✗ Important Note: This is not an isolated issue - multiple users are experiencing the same problem with the GHL integration, which suggests this is an infrastructure/configuration issue on Vapi's side rather than a user-specific problem. Request: Please review and update: CORS policy to allow GHL OAuth callback domains CSP directives to support the OAuth flow QUIC protocol handling for the /events endpoint I've attached screenshots of the browser console errors for your engineering team's reference. Please prioritize this as it's blocking a critical integration for multiple users. Let me know if you need any additional diagnostic information. Thank you for your assistance.
https://cdn.discordapp.com/attachments/1451560639981031424/1451560640744525864/preview.webp?ex=69829af1&is=69814971&hm=17e006aa4d175886dc72f979760610800738b1e6a607c9c0577b6ed79d55e68b&
https://cdn.discordapp.com/attachments/1451560639981031424/1451560641415352424/preview_1.webp?ex=69829af1&is=69814971&hm=eca3278e4d3a9a45500167398f34b2cd71de8e30b879f12da5a8711a05868f86&
https://cdn.discordapp.com/attachments/1451560639981031424/1451560641881051289/preview_2.webp?ex=69829af1&is=69814971&hm=b82739edcac4f4dd120a50d3fa81c26817cc5a1497c53932eea1525a7a7ffe20&
https://cdn.discordapp.com/attachments/1451560639981031424/1451560642728165477/preview_3.webp?ex=69829af1&is=69814971&hm=90deaf9bdf57e5efe27658ed2a27072fd98c1968bdeb21fe7e958c6c6c2067df&
c
Chiranjeet Mishra
01/07/2026, 6:36 PM
Hi, I am sorry for the delayed response. And thank you so much for providing extensive information about the GHL integration issue. Currently there is an ongoing issue related to GHL integration and it will be fixed by end of Q1 this year.
Previous
Next