The "This content is blocked. Contact the site owner to fix the issue." message in the WordPress block editor is not a WordPress bug — it is almost always caused by your own security headers. On a typical Nginx setup there are two independent problems at play: a Content-Security-Policy that forbids the blob: URLs the editor needs to function, and a Permissions-Policy header whose syntax is invalid, so browsers discard it with a parse error.
Why security headers break the block editor
Gutenberg does not render the editing surface directly in the page. It builds an <iframe> whose source is a blob: URL, and it creates a Web Worker from another blob: URL for media handling. When your policy only defines default-src, the browser uses it as a fallback for the directives you did not set — including frame-src (which governs iframes) and worker-src (which governs workers). If default-src does not list blob:, both are blocked.
Each console message maps to one failure in that chain:
- The worker error means
worker-srcfell back todefault-src, which lacksblob:. - The framing error means
frame-srcfell back todefault-srcfor the same reason. - The
TypeError: Cannot destructure property 'documentElement'inblock-editor.min.jsis a side effect: the editor script expects the iframe document to exist, and it never loaded. - The
SecurityErrorabout a cross-origin frame appears when editor code tries to reach into the iframe that the policy already blocked.
The visible "content is blocked" notice is simply the editor reporting that its own iframe failed to load.
Fix the Content-Security-Policy
The clean solution is to declare frame-src and worker-src explicitly and allow blob: for exactly those two cases, while keeping the rest of the policy strict:
add_header Content-Security-Policy "default-src 'self' https: data: 'unsafe-inline' 'unsafe-eval'; frame-src 'self' blob:; worker-src 'self' blob:; base-uri 'self'; object-src 'none'; form-action 'self'; upgrade-insecure-requests;" always;
Once frame-src and worker-src are set, they no longer inherit from default-src, so the editor's internal iframe and worker load normally while scripts, styles, and images remain governed by the default rule. An alternative is to drop default-src entirely and keep only targeted directives such as base-uri, object-src, form-action, and frame-ancestors; that also unblocks the editor, but it leaves fetches, images, and styles unrestricted, so it is a weaker posture. Note that frame-ancestors 'self' is safe to keep — it controls who may embed your pages elsewhere, not what your own site embeds internally.
Fix the Permissions-Policy syntax
Permissions-Policy values must follow the HTTP structured field syntax (RFC 8941, updated by RFC 9651). Under that grammar, origin strings are delimited by double quotes only — single quotes are not valid delimiters — while self is a special token that stands alone. A directive such as camera=(self 'https://nginxhost') therefore fails the structured header parser, and the browser rejects the entire header.
Inside an Nginx configuration you have two ways to produce the correct quoting. Escape the inner double quotes:
add_header Permissions-Policy "geolocation=*, camera=(self \"https://nginxhost\"), microphone=()";
Or wrap the whole value in single quotes so the inner double quotes need no escaping:
add_header Permissions-Policy 'geolocation=*, camera=(self "https://nginxhost"), microphone=()';
The geolocation=* and microphone=() parts are fine as written; the parser stops at the first malformed token, which is why the error message gives no further detail.
Tracking down headers you never configured
If the console complains about a directive such as frame-ancestors that appears nowhere in your sites-available file, the header is being injected by another layer. Common sources include a security or optimization plugin emitting headers via PHP, a CDN or reverse proxy in front of Nginx, a hosting panel template, or a different server/location block that also matches the request. Inspect what is actually delivered:
curl -sI https://your-site.example/wp-admin/ | grep -iE 'content-security|permissions-policy|x-frame'
Beware one Nginx quirk while you are in there: add_header directives at the server level are ignored inside any location block that declares its own add_header. If a location block sets even one header, you must copy all of your headers into it or move them into a shared include file.
Verify the fix
Test the configuration and reload:
nginx -t && systemctl reload nginx
Then open the editor with the browser DevTools network tab set to disable caching, and hard-refresh. The blob framing and worker errors should vanish and the editor should render. The Permissions-Policy message is a console warning rather than a hard blocker of the editor, but fix it regardless: a malformed header means the browser silently ignores your whole permissions policy.
Frequently Asked Questions
Why does the block editor need blob: URLs at all?
Gutenberg isolates editing content in a sandboxed iframe and runs media-related logic in a Web Worker. Both are generated in memory as blob: URLs rather than fetched from a server path, so any policy that blocks blob: for frames or workers breaks the editor.
Is allowing blob: in CSP a security risk?
blob: URLs are same-origin and short-lived, and permitting them for frame-src and worker-src is standard practice for WordPress. It is far narrower than loosening default-src across the board.
Can I remove 'unsafe-inline' and 'unsafe-eval' now?
Not blindly. WordPress and many plugins still rely on inline scripts and, historically, eval-based code paths. Remove them only if you are prepared to add nonces or hashes and test the admin area thoroughly.
The browser still shows the old headers after I edited the config — why?
Check that the reload actually succeeded, confirm you edited the server block that really serves the domain, and remember the add_header inheritance rule: a location block with its own headers suppresses the server-level ones. Also disable browser caching or use a private window.
Does X-Frame-Options: SAMEORIGIN interfere with the editor iframe?
No. The editor's iframe is a same-origin blob: document, so SAMEORIGIN is satisfied. That header only restricts other sites from framing your pages.
What exactly does the structured header parser error mean?
It means the header value violated the structured field grammar — in practice, an origin written with single quotes instead of double quotes. Replace them (escaping as needed in Nginx) and the warning disappears.