CORS Policy Issue with Gutenberg Script from External Domain

  • Hello Community,

    I’m facing a CORS policy issue when loading Gutenberg scripts (navigation.min.js and index.min.js) from an external domain (https://s4md00.p3cdn1.secureserver.net) onto my site at https://transsocial.org. The browser blocks these scripts, citing the absence of the Access-Control-Allow-Origin header.

    Additionally, I observed that the failing requests for Gutenberg scripts carry the Sec-Fetch-Mode: cors header, contrasting with successful script loads that use Sec-Fetch-Mode: no-cors. This suggests a potential misconfiguration in how Gutenberg handles the mode of script requests.

    Is this a known issue with Gutenberg, and are there recommended workarounds or fixes? Adjusting the script tag or request mode seems necessary, but I’m unsure how to proceed within the WordPress framework.

    Appreciate any advice or solutions that have worked for you.

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Moderator jordesign

    (@jordesign)

    Hi @transsocial – can you tell me a little more about why you’re requesting those Gutenberg scripts from an external domain?

    Thread Starter transsocial

    (@transsocial)

    Hi @jordesign, our website is a managed WordPress through GoDaddy, and that’s how they made it work.

    Moderator jordesign

    (@jordesign)

    Hey @transsocial – given that it looks like they have some kind of custom setup for that – I’d reaching out directly to GoDaddy’s support to see if they can find out why that is happening.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘CORS Policy Issue with Gutenberg Script from External Domain’ is closed to new replies.