Avast WEBforum

Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Beta - Avast => Topic started by: NON on March 07, 2016, 02:18:47 PM

Title: [Resolved][11.1.2254] Sign-in into avast account failed
Post by: NON on March 07, 2016, 02:18:47 PM
Hello all,


my avast has failed to login to Avast Account for some time (maybe since this beta period starts).
Repair nor clean reinstall does not solve this issue.

With last stable version 11.1.2253, everything went fine.

Avast: 11.1.2254 Premier / Pro
Windows 7 SP1 64bit
Title: Re: [11.1.2254] Sign-in into avast account failed
Post by: DavidR on March 07, 2016, 02:44:52 PM
Are you able to log on to your my.avast.com account from your browser ?

If so it does seem to be pointing to an issue with the beta - I'm not on this beta, but I think this could also be an issue with my.avast.com. When I log on using my browser, this PC isn't displayed as a device.

After a couple of attempts I was able to connect to my.avast.com account from the program user interface. Even this device isn't shown.
Title: Re: [11.1.2254] Sign-in into avast account failed
Post by: NON on March 07, 2016, 03:07:12 PM
Hello DavidR, thank you for the reply.

I can log-on to my.avast.com from browser, however details of some of the devices cannot be shown.
Devices are listed there, but when I open these devices my.avast.com just returns error message.
This indicates my.avast.com has some issue. :(
Title: Re: [11.1.2254] Sign-in into avast account failed
Post by: DavidR on March 07, 2016, 04:54:35 PM
Yes I think that it is more likely to be an issue with my.avast.com than specifically the beta build as there were some anomalies even with 11.1.2253.

Of course your error message (attached image) mentions Avast Passwords and I don't have that installed.
Title: Re: [11.1.2254] Sign-in into avast account failed
Post by: NON on March 12, 2016, 07:52:19 AM
Confirmed fixed in 11.1.2255.

Issue with device details is still there though, but I think this is my.avast.com issue as DavidR suggested, not this beta.

So, marked as fixed. :)