Potentially suspicious site coming up on Render

[Ryan_Scott]

Describe the problem/error/question

On Render, usually if I restart the server and reload any n8n pages, I get the red screen of suspicion, and then Render is notified and shuts down my account. I’m not sure 100% if its tied to rebooting or not.

What is the error message (if any)?

This site is suspicious.

Please share your workflow

Does it with no workflow at all.

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

• n8n version:
  the latest as of yesterday from docker library
• Database (default: SQLite):
  default
• n8n EXECUTIONS_PROCESS setting (default: own, main):
• Running n8n via (Docker, npm, n8n cloud, desktop app):
  docker
• Operating system:
  Render

Render will shut down my entire account from this, making n8n entirely unworkable as a solution. I saw a thread about this previously. While I’m willing to work on N8N cloud I would rather self-host it in the cloud. I don’t see any solution but the thread was closed last year.

Potentially Suspicious code. Google marked site as phishing

Describe the issue/error/question Hello today’s morning my root domain and all of the subdomains was taken off google and marked as deceptive and dangerous because of phishing danger. One of the very few changes I made recently was updating n8n self-hosted (docker). I already rejected other possibilities. Only clue is that one of free scanners I use detected “Potentially Suspicious files” on my n8n site. This is my very only clue at this moment. Can somebody tell is this normal? I’ll keep searc…

[mariana-na]

Hi @Ryan_Scott ,

Welcome to the community!

I regret to see that is issue is back.
Could you share what version of n8n you are currently on?

And have you ran the Online Website Malware Scanner check?

This would be helpful information to track the issue - I will also flag our team so we can re-evaluate this

[mariana-na]

The recommendation we have for affected users at the moment is to use a subdomain which is not “n8n”.
Some use cases have also been successful in requesting revalidation from Google, through their webmaster tools, where Google approved user requests and removed the warning

Could you give this a try and let me know how you get on?

[Derek_Cheung]

I’ve been using railway.app and I haven’t had any issues at all. I’ve found that cloud provider a bit less expensive than render as well.

I’m happy to share with you the one-click deployment template I made to make it easier Deploy n8n-flowise-ai-automation on Railway | Railway

[jb8n]

FYI, I had it a year or two ago.
Until yesterday, I was fine with a 4-month old version.
yesterday, I updated to 1.49.0, and I have the red screen systematically now.

My subdomain is n8n and I don’t wish to change that. I’ll try telling google about it again …

[jb8n]

FYI again, following my post yesterday, I added my domain to the Google Console, it immediately picked up that a subdomain (n8n.) had an issue. I requested a review, and within a few hours I got an email from Google mentioning that the review was successful. Today, no more red screen or “dangerous” labels on n8n.mydomain.tld