Troubleshooting

Find solutions for common errors and issues when using n8nmanager.

"Dangerous site" Browser Warnings

If you see a red Dangerous site warning in Chrome or Edge on a brand-new instance, this is not a certificate problem — your SSL is fine. The warning comes from Google Safe Browsing, which flags newly-registered domains with password input fields because they look statistically similar to phishing sites.

The quick workaround

Because the n8n subdomain is frequently used by new instances, Google's automated filters can sometimes be overly aggressive against it. Often, the fastest way to resolve this issue is simply to change your subdomain.

For example, change n8n.yourdomain.com to automate.yourdomain.com, workflows.yourdomain.com, or something similar. This avoids the flagged subdomain entirely and usually bypasses the warning immediately.

The official resolution

If you want to keep your current subdomain, you can request a review from Google:

  1. Verify the domain in Google Search Console. Go to search.google.com/search-console, add your domain, and verify ownership via DNS TXT record.
  2. Open Security & Manual Actions → Security Issues. Google will show the specific reason it was flagged.
  3. Click Request Review and explain that the instance is a private workflow-automation tool for your team, not a public login page. Reviews typically take 1–3 days.
In the meantime, keep the instance off public traffic. Restrict access via an IP allowlist or a reverse-proxy auth layer (Cloudflare Access, oauth2-proxy) — the fewer unauthenticated crawlers that see the login form, the faster the warning disappears.