@nduchon would be great if you could please post all the texts + links here so I can put them in Google Translate. Maybe it contains some helpful information that helps us understand why they now start complaining about the sign-in page. Thanks a lot!
Can you explain if those changes will influence the functionality of n8n workflows running when I am not logged in in any way? Just want to make sure before I update.
About two weeks ago, my emails started ending up in spam (the ones I sent via n8n workflows) and my whole domain was blocked. I couldn’t figure out what the problem was (I learnt a ton about Wordpress in the process;)
I didn’t think that had anything to do with my n8n instance, and after a week I got everything back up and running.
Today, I got the email about the n8n subdomain causing the issue.
I hope that since Google has already had this issue reported, removing the flag shouldn’t take long.
Hey @Rafix,
There is no reason to think that the changes will impact the workflows running when not logged into n8n.
The change stops parts of n8n loading in a browser that is not logged in so a bot crawling / indexing your site won’t be able to see bits that are not needed.
n8n workflows once scheduled will run server side and not from a browser, webhooks are also not impacted.
I installed a new n8n (0.222.1) on a new vps yesterday. After an hour he already had this message on the n8n login page. Today all pages on the main domain and subdomains are showing this alert. I’m going to request the review on Search Console now.
If any of you are still seeing this issue, can you please scan your domain using Online Website Malware Scanner and DM me a link to the results?
That might help us narrow down what might be causing this.
Hi @netroy
Just did the scan and it shows green with minimal risk
Mine is clean as well. 0 on anything suspicious.
I updated to version 0.222.1 on Friday, after I found this thread and asked Google to review it.
Funny thing is that Google cleared it this morning and flagged it back again two hours later.
@netroy We have also been facing this issue for days. Here is the result of the test: Quttera - Detailed Malware Scan Report
Mine still shows the red flag from Google…
@netroy unfortunately my entire website is down. I passed the url of my n8n on this site and here is the result:
@luizeof Looks like your site is back up now as I can access it. Do all of your sites go through cloudflare? I set up an n8n instance yesterday and added it to the Google Search console but it has still not been blocked.
The potential fix for this is now available in 0.224.0.
PS: 0.224.0 is not marked as stable yet, so please make sure to backup your databases before the upgrade 
I basically said that n8n is a software automation program that allows us to run processes between applications (similar to zapier) and that it is for internal use not intended for public use. We don’t solicit user information.
I’m using the n8nio/n8n:0.224.0-debian image, and Qutterra no longer reported the problem:
@Jon I understand that n8n has to be used at our risk, but given the seriousness of the problem with the library and the fact that our domain and our clients are being marked as phishing … couldn’t there be an emergency release with this fix? we have almost 3 very bad weeks for anyone using n8n. Please consider this… we in the community are in serious trouble.
Thanks for ALL your efforts
Hey @luizeof,
I am not sure I fully understand the question there, We have released 0.224.0 which contains the fix and we are about to release 0.224.1.
Are you asking if we can release older versions of n8n with the same change?
Hi @Jon, thanks for your time.
These are small details, but they make the difference for those who don’t know much about docker, containers, versions, etc.
the latest tag still does not have the correction (0.222.2), I believe that because it is a pre-release on github. Technically there is no such “official” fix. Netroy suggested the 0.224.0 tag as a fix, but it’s still not marked as stable. This causes a bit of confusion.
I talk to a lot of non-technical people and it’s hard to suggest a fix for these people. I think the latest tag is easier, a lot of people end up using this tag instead of more specific tags. Placing the fix as stable would be nice too, as it removes the fear that the fix will cause other issues.
I reiterate that I fully understand how this works and my installations and people in my members area are already using 0.224.0, but I see that the general public who talk to me has these doubts.
Hey @luizeof,
Perfect so what you are asking is if we can release older versions with the same change. Let me check what the plan is there.