Avast (anti virus) web shield (PC) aborts log in to Atlassian because there is a threat?

[Gidon Burcat]

Hi, I was a Trello user for a few years, recently automatically migrated to Atlassian.
I didn't look into Atlassian too much, so I guess I have a default  standard setup.

I use Trello a lot, and my credentials are saved on chrome. 
Since I've done some browser cleaning, I am trying to log into Trello > sends me to Atlassian > my Avast anti virus pops up this message:

How can this be solved?

Thanks

Gidon

[Gidon Burcat · Accepted solution]

I think it has been fixed now....

I didn't add any exception, and I am able to connect.

[addsum]

It is working for me now as well, and without doing anything.

[Al Keeling]

HTML:Script-inf[Suspected]  ?   Maybe a false positive.   Open Avast, go Menu > Settings > General > Exception >  add URL https://id.atlassian.com/login

[Gidon Burcat]

Hi, I thought of it, but why was it changed today?
There could be 2 possibilities:
1. Some code was changed in the login page that made avast suspicious?
2. The login page has been hacked?
I wonder if we can get an official answer from Atlassian.

[Deleted user]

Just noting that I ran into this issue, and tried adding an exception. The result was a loop of redirects. Still blocked.

[Alexander Nitsch]

I second this. Same problem here. Super annoying.

[shershov]

Same problem.

[Fabian De Sanctis]

Same Issue !!!!

[addsum]

Two more of us having the same issue that started today:

https://community.atlassian.com/t5/Jira-Questions/Cannot-login-from-avast-quot-We-ve-safely-aborted-connection-on/qaq-p/1413741

[Robert]

Same problem with AVG too. And resetting the password does not send a new password option either to my email account.

[Robert]

Take that back. Finally got a reset but still can't log in with the threat.

[Robert]

Discovered you can not raise a support ticket because you need to log in. And the anti virus won't let you. Also sending an email to support@atlassian.com sends back an automated email sending you to support login.

Twitter next I suppose.

[Gidon Burcat]

That's correct, you can't call for support if not from inside.

And the fact that AVG found it as a threat too, makes it a major problem for Atlassian.

[Deleted user]

This is working for me now. Still have an exception added just in case.

[Lyn Cox]

Avast user.  Fixed now.  Can login without the threat popping up.

[Nicholas Eisner]

Same problem logging into Jira. Reported to Atlassian Support. I can't believe they didn't know this until now.

[Jan Rodríguez]

Same here! I'm unable to log in, so it's big problem. I hope it get fixed soon, or at least that they post something official.

[Robert]

I've had a reply via Twitter to add exceptions to various addresses into my AVG. Just trying it. I don't know if it will work before you ask!

https://confluence.atlassian.com/cloud/atlassian-cloud-ip-ranges-and-domain-744721662.htmls 

[addsum]

I think they need to first disclose why the behavior changed between today and yesterday (since that link also was last modified on the 18th), and specifically address the message first posted here with respect to the HTML script, and also why it would impact both AVG and Avast.

[Robert]

Just removed all exceptions from AVG too. Seems all right. Back to normal.

[Deleted user]

This is also happening to me. Adding an exception `https://id.atlassian.com/*` did not resolve, and seemed to expose another alert:

[Al Keeling]

Add exceptions in Avast as endpoints without wildcards * or parameters.  In other words, the login endpoint should be:  https://id.atlassian.com/login    Then restart your browser.

[Deleted user]

I removed the wildcard and was still having issues, but it seems to be resolved now.

[Lyn Cox]

Same issue.