HTTP error (403) during update attempts

Avast Free Antivirus / Premium Security
1

Howdy, from a couple of weeks I’m receiving this error when I try to update Avast (both definitions and software)
I’m almost certain it’s an issue connected to Proxy/Firewall etc, but of course I could be wrong.

How can I find it out exactely? How can I know what do I have to do to solve it? (ports to open etc)

The installed version at the moment is 8.0.1483
The virus definition is the la 130314-1 released on 14/03/2013

2

try installing the VPS and see if this changes anything http://www.avast.com/download-update

3

Ok, trying right now.
What is this VPS for btw? It mentions Avast up to 7, while I currently have version 8 installed.

What’s strange is that update used to work just fine up to 2 weeks ago, which makes me think something in my network has been changed without me knowing it.

4
What is this VPS for btw?
it is the virus signatures for manual download.....released once a day i think if you have a computer that is not online, you can download and transfer using a usb stick
It mentions Avast up to 7, while I currently have version 8 installed.
yes but it should work for 8.....lots of suff on the website is not updated for 8 yet....like the help guide
5

That worked and it updated my Avast just fine (thanks!!!) altough if I try to launch a new update I still get the same 403 HTTP error and I still have no clue what could possibly be the cause of this and how to solve it.

Any further clue on what it could depend on?

6

check the program update settings…
you may try direct connection no proxy…any change?

7
  • Which avast!..?? (Free/Pro/IS/Premier)
  • Which version…??
  • OS…?? (32/64 Bit…? - which SP…?)
  • Other security related software installed…??
  • Which AV did you use before avast!..??
8
  • Free
  • 8.0.1483
  • Win7Pro x64 completely up to date with WinUpdate
  • Uhm Windows firewall? Nothing else specific installed locally
  • I’ve been used Avast for like the, uhm… past 6 years? Or something like that.

@Pondus
Putting uptate settings to direct connection appearently solved the issue :smiley: Thanks a lot! ^^