-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document how to troubleshoot when the Matomo instance is showing a warning Chrome due to being added to safe browsing list (or other reasons) #20246
Comments
This issue has been mentioned on Matomo forums. There might be relevant details there: https://forum.matomo.org/t/chrome-displaying-red-screen-saying-deceptive-site-ahead/49178/5 |
This is more likely caused by bad IP address reputation (checked with https://scamalytics.com). The reported instances both have scam / fraud scores > 70 |
This looks a lot like your Matomo domain is on the google safe browsing list. And report an incorrectly blocked site here: |
@sandrocantagallo Did someone from Google tell you that you need to remove the tracking to be removed from safe browsing list, or is that an assumption from yourself? |
Is maybe the domain of the matomo instance on the safe browsing list, causing all sites using that instance to land on the list as well? |
I'm unfortunately not deep enough into that topic to provide a solution. Also I doubt there is much we can do in the code to solve that issue. Maybe someone else has an idea here... |
Just installed Matomo on a sub domain of my plex....same issue as yours. I had inactivated the sub domain and deactivated the plugin WP matomo....only by this way the red flag is removed by Google. Finally how can you enable matomo ??? I don't understand if it feasible to use it if google is blocking automatically.... |
Here I think we would want to create a FAQ to explain how to troubleshoot this use case: imagine your Matomo instance has this problem suddenly, then you expect Matomo to have an FAQ to clearly explain why, the next steps on what to do. Re-opening and renaming issue to restrict scope. |
Hi @mattab |
So far we have no evidence that there is an issue with this, so we would want to document to the rare people who have an issue like this, how to learn more about the issue. Then in the FAQ we could mention they can reach out to us if they still don't know / understand. Then we could learn if there are some strange things happening. But hopefully not. |
I don't know if that can help but on my side, after the matomo deployment, I also installed GA extension in order to retrieve my GA3 data to matomo . By this way, I received an alert email from Google just before the warning page. I stopped the GA import, deactivate the WordPress plugins and automatically my site was again visible. I requested google to analyse my website and 2 days after I received a clear answer. So I reactivates matomo plugin to track data....no more issue.... everything is ok since 2 weeks Cross the fingers ! |
Last friday google marked my site with self-hosted Matomo analytics as fraud. Classic red banner. Removed Matomo script at saturday and today (monday) everything is okay. Unlucky, gonna migrate to another analytics provider. |
Hi @vlakam
See: |
@heurteph-ei Understandable. But i can't afford this risk. Another analytics platform (not GA) does not trigger google warning so i stick with them at the moment |
I just had this issue happen twice. I did a review request and everything was going well for about five weeks and then the red screen came back. Unfortunately I don't see a legit way to put this code on cleints' sites without doing a server to server implementation. Unless anyone else here has some ideas. |
Same Red page after one month without troubles. |
Hi @CyrPen. |
Thank U @heurteph-ei, i finally found an issue by :
Regards, |
This issue has been mentioned on Matomo forums. There might be relevant details there: https://forum.matomo.org/t/chrome-displaying-red-screen-saying-deceptive-site-ahead/49178/20 |
Same issue here. Interested to find out why Google flags these as deceptive. Is it because of something in the Matomo web interface, and therefore all instances are likely to get flagged? (Google Search Console reported that the index.php URL was flagged) Or is it because the tracking code tracks sensitive information? If it’s very common, maybe it should be part of the installation / setup instructions to set up Google Search Console to monitor it. |
I think that the Matomo login page looks identical for everyone. This could be seen as suspicious by Google. Maybe outputting the name of the current domain in the page content, or an option to set your own logo, would make all instances look unique and potentially less suspicious. |
This issue has been mentioned on Matomo forums. There might be relevant details there: https://forum.matomo.org/t/le-site-web-que-vous-allez-ouvrir-est-trompeur/51178/3 |
This issue has been mentioned on Matomo forums. There might be relevant details there: https://forum.matomo.org/t/chrome-displaying-red-screen-saying-deceptive-site-ahead/49178/29 |
This issue has been mentioned on Matomo forums. There might be relevant details there: |
This issue has been mentioned on Matomo forums. There might be relevant details there: https://forum.matomo.org/t/chrome-displaying-red-screen-saying-deceptive-site-ahead/49178/32 |
This issue has been mentioned on Matomo forums. There might be relevant details there: |
The same issue happened to me today. I've just finished the installation and placed the instance on subdomain of the website that I have in Google Search Console. A day later I come and see that my website have phishing and deceptive pages issues. |
Has any progress been made on this? We've been only using Pixel tracking with our on-premise, as our installation was repeatedly flagged by Google when we were trying to use javascript during setup. |
This issue has been mentioned on Matomo forums. There might be relevant details there: |
trying to open my website, where Matomo code installed and here is what it shows:

after deleting Matomo code, everything works okay.
The text was updated successfully, but these errors were encountered: