My filebrowser subdomain got marked as malicious by Google and they blocked my whole domain... Removed filebrowser docker and now I'm clear again...

[singularity098]

So my whole domain got blacklisted by Google Safe Browsing. I have maybe half a dozen subdomains on this domain for various applications that I use. I was baffled, but eventually I was able to associate the domain to my Google account and could then log in and see that the reason was specifically the filebrowser subdomain that I had. This is what the Google Search Console told me.

It was flagged for potential phishing. It was all very unclear and vague actually. But after removing the filebrowser subdomain from my certificates, taking it offline, and resubmitting for review, Google did take me off of the blacklist.

I really liked this application, but I'm afraid to re-enable it and continue using it for fear of going through this again... especially if I'm relying on my own server outside of my home on vacation or something. (it took weeks and was even blocking me from using my own Jellyfin server within my own home... Google really has their tendrils in my life more than I thought)

Is there any kind of known issue? Has this happened to anyone else?

Details of my setup is that I'm running an Unraid server with the official filebrowser/filebrowser docker image. I have a swag reverse proxy with a port forward for SSL port 443, and the certificates are fully signed by Let's Encrypt and valid. My File Browser install has full authentication enabled, so I don't think they could have seen anything besides the login page.

It did specifically show the redirect as maybe being a problem. Example:

http://filebrowser.mydomain.com/
... redirects to ...
http://filebrowser.mydomain.com/login?redirect=%2Ffiles%2F

As if that was a problem. I don't really understand wtf Google's problem was.