Roll20 uses cookies to improve your experience on our site. Cookies enable you to enjoy certain features, social sharing functionality, and tailor message and display ads to your interests on our site and others. They also help us understand how our site is being used. By continuing to use our site, you consent to our use of cookies. Update your cookie preferences .
×
Stuck in a login loop? Try manually signing out and back in before launching your game. Otherwise, contact the Help Center!
Create a free account

Roll 20 hacked? Phishing cookies being blocked by Avast

1681430879
Bill K.
Pro
Sheet Author
Today, every page I load on Roll20, Avast antivirus spazzes out and says it's blocking dozens to over a hundred tracking cookies. This has never happened before - is it happening for anyone else? And example is: "We've blocked a threat URL:Phishing &nbsp;on <a href="https://s3.amazonaws.com/files.d20.io/images/275893110/e-VX9U8KiyK5b0Q9Za8PXQ/med.jpg" rel="nofollow">https://s3.amazonaws.com/files.d20.io/images/275893110/e-VX9U8KiyK5b0Q9Za8PXQ/med.jpg</a>" &nbsp;from being downloaded.
1681437103
keithcurtis
Forum Champion
Marketplace Creator
API Scripter
Hi Bill! This sounds very much like something Roll20 pushed out an experimental hotfix to combat last week. Basically,&nbsp;these aren't phishing links; they're just normal images stored in s3 in Amazon Web Services, which Roll20 uses for image serving. Avast's smart filter is being overzealous with things stored in s3 since their last patch. You might see this on some other websites as well. You can read more about it and how to get around the issue here , in the Help Center.
1681601024

Edited 1681601037
This problem started affecting me today... I tried the solutions in the Help Center thread, to no avail. For now at least, I have to completely disable AVG when I want to use Roll20.
1681604059
keithcurtis
Forum Champion
Marketplace Creator
API Scripter
Hi Brett, I suggest reaching out to the team through a&nbsp; Help Center Request . Be sure to mention that you have tried the solutions on that linked page. I'm sure they'd appreciate the insight.
I turned AVG back on, and now it seems to be WAI. Maybe it just took awhile for AVG to register the changes in settings.