My emby server has been flagged as a Deceptive site.

[Luke 42077]

2 hours ago, Dickydodah! said:

To test my theory I changed it back to "Emby" and it was blocked within a minute and when I changed the server name to my domain name (not containing Emby) it work again within a minute.

@LukeIs this something that can be tested and investigated as I was using more of a "poke and hope" approach and know next to nothing about DNS etc.

We'll take a look at it. Thanks.

[marlon006 1]

I’ve been using emby.domain.tld as a subdomain without issues for over a year now, initially with HAProxy and, for the past 6-7 months, with Nginx Proxy Manager. While everything runs smoothly, I’ve occasionally encountered issues where Chrome/Google flags the subdomain as unsafe.

In my experience, this has happened around 4 times over the years. At one point, it was really bad, and I had to resubmit the site for review over a few days. Each time, I reported it as a false positive and patiently waited for Google to unflag the domain. It’s worth noting that I’ve never changed the domain itself during these incidents, which might explain why the issue hasn’t been more frequent. However, I did recreate a secondary subdomain, emby2.domain.tld, which is IP-whitelisted, so I always have an unflagged backup ready to go whenever the issue arises.

I believe the last time I was affected was before I re-implemented HAProxy (around 1.5 years ago). Since then, I’ve used both Nginx and HAProxy together.

I suspect that changing domains could increase the likelihood of getting flagged by Chrome/Google, even if the configurations remain secure. Despite these occasional setbacks, I’ve successfully hosted Emby on emby.domain.tld for years, with varying configurations, without major issues.

TL;DR:
Changing subdomains on the fly doesn’t improve your site reputation, and it might even decrease it.

[Carlo 4560]

Where, and how are you getting this error?
What is the exact error you get?

This could be a cert error of some type or you are running some type of 3rd party app or DNS provider using 3rd party lists of "safe domains" that is the source of the problem.

You can always flag your own domain or any other as safe in the browser to bypass an issue like this.