Login Page Fails to Load – Missing JS Resources and 403 Errors on n8n Cloud

Questions
1

Describe the problem/error/question

I’m unable to access the login page of my n8n Cloud instance. The page fails to load properly, and several critical frontend resources return errors. This issue has persisted across multiple browsers, devices, and networks, even after clearing cache and using incognito mode.

What is the error message (if any)?

From browser dev tools (F12), I consistently see the following errors:

  • GET /assets/polyfills-BGt12fxg.js → 404 Not Found
  • _MapCache-CaP4mhI9.js:2001 → Uncaught SyntaxError: Unexpected end of input
  • signin:1 → **Uncaught (in promise) Object`
  • content.js:5215 → **Uncaught (in promise) { code: 403, httpStatus: 200, httpError: false, name: ‘i’ }`

These errors suggest that the frontend build is missing required JS files, and the login flow is failing due to a backend permission or token validation issue.

Please share your workflow

Not applicable — I cannot access the canvas due to login failure.

Share the output returned by the last node

Not applicable — no workflow execution is possible at this time.

Information on your n8n setup

n8n version:
Unknown (hosted on n8n Cloud)

Database (default: SQLite):
Managed by n8n Cloud

n8n EXECUTIONS_PROCESS setting (default: own, main):
Default (Cloud-managed)

Running n8n via (Docker, npm, n8n cloud, desktop app):
n8n Cloud

Operating system:
Browser-based access (tested on Windows 11, macOS, and mobile)

2

This looks like a n8n Cloud infrastructure issue rather than a configuration problem on your end. Since you’re seeing 404 errors for core JavaScript files and 403 permission errors, it suggests there’s a problem with the n8n Cloud deployment or CDN serving your instance.

I’d recommend:

• Contact n8n Cloud support directly through their official channels - this appears to be a backend/infrastructure issue they need to resolve

• Check the [n8n status page](https://status.n8n.io) to see if there are any ongoing outages in your region

• As mentioned in the [support.n8n.io](Troubleshooting Login Issues | n8n Help Center) troubleshooting guide, if you were on a free trial that expired, you might need to request a magic link at n8n.cloud

Since this is affecting core frontend assets and you’ve already tested across multiple browsers/networks, it’s definitely something that needs to be escalated to the n8n team rather than being a local browser or configuration issue.