our TeamCity site flagged as "deceptive site" by google chrome (and firefox)

Without knowing what the "Details" part of the page says it's hard to say, but usually this means that chrome has detected something weird on the page. Since it started happening after upgrading octopus, the first idea would be to roll back that upgrade or even disable the plugin by accessing the data directory, plugins subfolder and moving the plugin out of the way. If that fixes the issue, please report it to octopus directly, since they are the developers of the plugin

If that doesn't fix the issue, then we would need more info, the details button might show something useful, or maybe using a different browser could help.

Hi, The details page doesn't give anything really 

We used google webmaster tools to get more details about the problem, but google doesn't really help here

The new version of the plugin has been disabled immediately, but I really doubt that the plugin itself could become a problem. 

However, what about the "one-click plugin installation" mechanism being perceived as a problem by google?

I used that mechanism to upgrade the Octopus plugin. The experience was so nice, by just click-click, not needing to worry logging into server, etc. 

Could the mechanism be a problem to google?

While it isn't impossible, this mechanism is used for the vast majority of plugins, and a good amount of our own developers, testers, support engineers, etc use chrome to test and I am not aware that any of us has seen this screen before.

When does this screen show up? Is it directly at the base url of your installation? Does it only happen for some specific pages?

Hi Denis,

While we still didn't get to the bottom of the problem, my current suspiction is that the issue is not with TeamCity, but with the dns that it's under, as all other sites that are with same-root subdomains are affected. It was just very suspicious that the "Deceptive" warning has started to occur very shortly after doing the upgrade.

Thank you for sharing information that none of the users has reported anything similar and these mechanisms are widely as well - it's good to know that it's unlikely that TeamCity is the source of the trouble.

We're going to migrate our TC setup anyway soon, so I think this will solve the problem for us.

Thanks for all help anyway and good luck with (very good!) product