Script error. JavaScript Origin: On your device Last updated 11 Oct 2026

Script error. (at line 0) — cross-origin error details hidden

An error happened in a script from another origin, and the browser hid the details.

Exact message you may see Script error.Script error at line 0
Explore the map of this error Full error map →
Seen on: JavaScript

Meaning

Browsers redact errors from cross-origin scripts unless the script is loaded with crossorigin="anonymous" and served with Access-Control-Allow-Origin.

Common causes

  • Third-party/CDN scripts without CORS headers
  • Your own bundle on a CDN domain without crossorigin attribute
  • Browser extensions injecting scripts

⚡ Quick fix

  1. Add crossorigin="anonymous" to script tags and CORS headers on the CDN
  2. Filter "Script error." noise in monitoring

Detailed fix by platform

JavaScript

  1. <script src="https://cdn.example.com/app.js" crossorigin="anonymous"></script>

How to diagnose

  1. Source — Which script origin?
  2. Headers — CORS on the script response?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: On your device. Errors that are often confused with or caused by this one (click to open):

AbortError — AbortError: The user aborted a request. / signal is aborted without reason (JavaScript)AbortErrorblocked a frame — SecurityError: Blocked a frame with origin "x" from accessing a cross-origin frame. (JavaScript)blocked a framebody already used — TypeError: Failed to execute 'json' on 'Response': body stream already read (JavaScript)body already usedCORS — CORS Error: No 'Access-Control-Allow-Origin' header is present (API)CORScross-origin error — Error: A cross-origin error was thrown. React doesn't have access to the actual error object in development. (React)cross-origin errorCSP violation — Refused to load the script because it violates the following Content Security Policy directive (JavaScript)CSP violationFailed to execute postMessage — Console: Failed to execute 'postMessage' on 'DOMWindow': The target origin provided ('https://a.com') does not match the recipient window's origin ('https://b.com') (Browser)Failed to execute pos…Mixed Content — Mixed Content: The page was loaded over HTTPS, but requested an insecure resource (API)Mixed ContentScript er…

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.