The console errors point to a Content-Security-Policy (CSP) issue.
Required frontend resources are being blocked, which causes the n8n editor to partially fail and results in a blank workflow canvas.
This is a frontend issue only (the backend and workflows are fine).
Adjusting or removing the CSP header at the proxy / platform / browser security layer usually fixes it immediately.
You can confirm this by checking DevTools → Console for CSP violations.
(Please note I am diagnosing from ChatGPT, I am non/semi-technical).
I pulled the CSP header from the main document response and it looks like this (trimmed):
worker-src ‘self’;
I’m on n8n Cloud, not self-hosted, so I’m not setting CSP myself.
From what I understand, the editor depends on web workers (likely blob-based), and with worker-src restricted to ‘self’ only, those workers get blocked. That would explain why the workflow canvas is blank even though:
• All Fetch/XHR requests are 200
• Only Sentry telemetry calls are failing (403)
• No meaningful JS errors show in console
• Issue reproduces across browsers and in incognito
Can you confirm whether the current Cloud CSP is missing blob: for worker-src (or equivalent), and if so, update it?
Sorry for the lack of attention, you’re right, on n8n Cloud there’s no way to act on the CSP.
In this case, the best next step is to contact n8n Support or your workspace owner so they can inspect the CSP actually served to your Cloud workspace, verify whether worker-src (or the equivalent script-src / default-src) needs blob: for the editor workers, and apply or roll out a fix on the Cloud side if needed.
