←back to thread

Google flags Immich sites as dangerous

(immich.app)
1291 points janpio | 2 comments | 22 Oct 25 20:53 UTC | HN request time: 0.408s | source
Show context
david_van_loon ◴[23 Oct 25 02:50 UTC] No.45677671[source]▶
I'm fighting this right now on my own domain. Google marked my family Immich instance as dangerous, essentially blocking access from Chrome to all services hosted on the same domain.

I know that I can bypass the warning, but the photo album I sent to my mother-in-law is now effectively inaccessible.

replies(6): >>45678334 #>>45678991 #>>45679119 #>>45679309 #>>45679692 #>>45682820 #
wiether ◴[23 Oct 25 07:17 UTC] No.45679119[source]▶
No later than last weekend I was comtemplating migrating my family pictures to a self-hosted Immich instance...

I guess a workaround Google's crap would be to put an htpasswd/basic auth in front of Immich, blocking Google to get to the content and flagging it.

replies(3): >>45679498 #>>45681169 #>>45682665 #
1. skatsubo ◴[23 Oct 25 08:21 UTC] No.45679498[source]▶
Add a custom "welcome message" in Server Settings (https://my.immich.app/admin/system-settings?isOpen=server) to make your login page look different compared to all other default Immich login pages. This is probably the easiest non-intrusive tweak to work around the repeated flagging by Safe Browsing, still no 100% guarantee. I agree that strict access blocking (with extra auth or IP ACL) can work better. Though I've seen in this thread https://news.ycombinator.com/item?id=45676712 and over the Internet that purely internal/private domains get flagged too. Can it be some Chrome + G Safe Browsing integration, e.g. reporting hashes of visited pages?

Btw, folks in the Jellyfin thread tried blocking specifically Google bot / IP ranges (ASNs?) https://github.com/jellyfin/jellyfin-web/issues/4076#issueco... with varying success.

And go through your domain registration/re-review in G Search Console of course.

replies(1): >>45682771 #
2. david_van_loon ◴[23 Oct 25 15:12 UTC] No.45682771[source]▶
Thank you for the "welcome message" suggestion! I'll implement that in the hope it may help in the future.