Avast WEBforum

Consumer Products => Avast Mac Security => Topic started by: Brian Duncan on June 01, 2008, 04:49:52 PM

Title: Updater blocked
Post by: Brian Duncan on June 01, 2008, 04:49:52 PM
 Having used the avast for mac demo successfully for a couple of days, i found that it could not access updates this morning.  Thinking it might have expired, I purchased a one year licence, but still no updates. I have restarted the computer, re-launched avast and agent - still no luck. Any suggestions?
Title: Re: Updater blocked
Post by: zilog on June 04, 2008, 11:15:58 AM
Having used the avast for mac demo successfully for a couple of days, i found that it could not access updates this morning.  Thinking it might have expired, I purchased a one year licence, but still no updates. I have restarted the computer, re-launched avast and agent - still no luck. Any suggestions?

Hallo, this is strange - when firing update manually (the big button "Check Update"), is it still not available?
What the upgate does is accessing http://files.avast.com/files/latest/mac/400.vps
Please, try whether the URL is accessible or not.

regards,
pc
Title: Re: Updater blocked
Post by: zilog on June 04, 2008, 12:15:16 PM
Having used the avast for mac demo successfully for a couple of days, i found that it could not access updates this morning.  Thinking it might have expired, I purchased a one year licence, but still no updates. I have restarted the computer, re-launched avast and agent - still no luck. Any suggestions?

Hallo, this is strange - when firing update manually (the big button "Check Update"), is it still not available?
What the upgate does is accessing http://files.avast.com/files/latest/mac/400.vps
Please, try whether the URL is accessible or not.

regards,
pc

UPDATE: some desync problem was found on our servers and reported to administrator.
Title: Re: Updater blocked
Post by: narosis on April 02, 2012, 10:43:35 PM
This is what I see when attempting to update:

Performing vpsmac update (repository: http://download.ff.avast.com/mac/vpsmac, filedir: /Library/Application Support/Avast/files/defs/12040200/../../Setup/filedir, workdir: /tmp, instdir: /Library/Application Support/Avast/files/defs/12040200/..)
Resolving download.ff.avast.com...
Resolved as 95.211.90.158
Downloading http://95.211.90.158/mac/vpsmac/vpsmac.lat...
Cannot download http://95.211.90.158/mac/vpsmac/vpsmac.lat
Resolving download.ff.avast.com...
Resolved as 95.211.90.158
Downloading http://95.211.90.158/mac/vpsmac/vpsmac.lat...
Cannot download http://95.211.90.158/mac/vpsmac/vpsmac.lat
Resolving download.ff.avast.com...
Resolved as 95.211.90.158
Downloading http://95.211.90.158/mac/vpsmac/vpsmac.lat...
Cannot download http://95.211.90.158/mac/vpsmac/vpsmac.lat
Resolving download.ff.avast.com...
Resolved as 95.211.90.158
Downloading http://95.211.90.158/mac/vpsmac/vpsmac.lat...
Cannot download http://95.211.90.158/mac/vpsmac/vpsmac.lat
Resolving download.ff.avast.com...
Resolved as 95.211.90.158
Downloading http://95.211.90.158/mac/vpsmac/vpsmac.lat...
Cannot download http://95.211.90.158/mac/vpsmac/vpsmac.lat
Failed: cannot determine latest vpsmac version
Performing progmac update (repository: http://download.ff.avast.com/mac/progmac, filedir: /Library/Application Support/Avast/files/Setup/filedir, workdir: /tmp, instdir: /Library/Application Support/Avast/files/defs/12040200/..)
Resolving download.ff.avast.com...
Resolved as 95.211.90.158
Downloading http://95.211.90.158/mac/progmac/progmac.lat...
Cannot download http://95.211.90.158/mac/progmac/progmac.lat
Resolving download.ff.avast.com...
Resolved as 95.211.90.158
Downloading http://95.211.90.158/mac/progmac/progmac.lat...
Cannot download http://95.211.90.158/mac/progmac/progmac.lat
Resolving download.ff.avast.com...
Resolved as 95.211.90.158
Downloading http://95.211.90.158/mac/progmac/progmac.lat...
Cannot download http://95.211.90.158/mac/progmac/progmac.lat
Resolving download.ff.avast.com...
Resolved as 95.211.90.158
Downloading http://95.211.90.158/mac/progmac/progmac.lat...
Cannot download http://95.211.90.158/mac/progmac/progmac.lat
Resolving download.ff.avast.com...
Resolved as 95.211.90.158
Downloading http://95.211.90.158/mac/progmac/progmac.lat...
Cannot download http://95.211.90.158/mac/progmac/progmac.lat
Failed: cannot determine latest progmac version
Title: Re: Updater blocked
Post by: Kyowashiki on April 17, 2012, 12:11:41 PM
Dear Sirs

I had the same error message when I tied to update through a proxy server, which is properly described in Network Preference Pane.  But I could update successfully without a proxy server via the different network.  I'm afraid Avast for Mac cannot use the proxy server information in Network Preference Pane properly.
Title: Re: Updater blocked
Post by: Rainy on April 18, 2012, 10:55:25 PM
I have that issue, too and reported it a time ago...  :(

Anyhow,I could circumvent that by createing a firewall rule that allows to have direct access to http: (TCP Port 80) and maybe https (TCP Port 443) for download.ff.avast.com.

I hope that helps for now and much more I hope that proxy servers are supported within one of the next betas ;)

Regards
Title: Re: Updater blocked
Post by: zilog on April 19, 2012, 01:16:11 PM
I have that issue, too and reported it a time ago...  :(

Anyhow,I could circumvent that by createing a firewall rule that allows to have direct access to http: (TCP Port 80) and maybe https (TCP Port 443) for download.ff.avast.com.

I hope that helps for now and much more I hope that proxy servers are supported within one of the next betas ;)

Regards95.211.90.158
Hallo, there are 2 strange things:

1) why doesn't your DNS request contain 8 round-robin-rotated records, for download.ff.avast.com? Try repeatedly in terminal window "nslookup download.ff.avast.com" or "host download.ff.avast.com" - there must be at least few different IP addresses, typically 8, changed every time you do the command. Is this right? And does the update still do the buggy behavior?

2) the problem was fixed, the DNS record, pointing to 95.211.90.158 (dead server) was removed, so the primary cause doesn't exist anymore, but it's a question why 1) didn't help you.

Thanks for that bug, and anny feedback would be appreciated,
regards,
pc
Title: Re: Updater blocked
Post by: Kyowashiki on April 20, 2012, 03:56:37 AM
Hallo

Build # of My application is 36618-3.  Update is still not working under proxy server. Here is my error log.


Performing vpsmac update (repository: http://download.ff.avast.com/mac/vpsmac, filedir: /Library/Application Support/Avast/files/defs/12041701/../../Setup/filedir, workdir: /tmp, instdir: /Library/Application Support/Avast/files/defs/12041701/..)
Resolving download.ff.avast.com...
Resolved as 208.43.121.90
Downloading http://208.43.121.90/mac/vpsmac/vpsmac.lat...
Cannot download http://208.43.121.90/mac/vpsmac/vpsmac.lat
Resolving download.ff.avast.com...
Resolved as 173.193.216.165
Downloading http://173.193.216.165/mac/vpsmac/vpsmac.lat...
Cannot download http://173.193.216.165/mac/vpsmac/vpsmac.lat
Resolving download.ff.avast.com...
Resolved as 95.211.174.155
Downloading http://95.211.174.155/mac/vpsmac/vpsmac.lat...
Cannot download http://95.211.174.155/mac/vpsmac/vpsmac.lat
Resolving download.ff.avast.com...
Resolved as 95.211.174.155
Downloading http://95.211.174.155/mac/vpsmac/vpsmac.lat...
Cannot download http://95.211.174.155/mac/vpsmac/vpsmac.lat
Resolving download.ff.avast.com...
Resolved as 75.126.203.73
Downloading http://75.126.203.73/mac/vpsmac/vpsmac.lat...
Cannot download http://75.126.203.73/mac/vpsmac/vpsmac.lat
Failed: cannot determine latest vpsmac version
Performing progmac update (repository: http://download.ff.avast.com/mac/progmac, filedir: /Library/Application Support/Avast/files/Setup/filedir, workdir: /tmp, instdir: /Library/Application Support/Avast/files/defs/12041701/..)
Resolving download.ff.avast.com...
Resolved as 173.193.216.165
Downloading http://173.193.216.165/mac/progmac/progmac.lat...
Cannot download http://173.193.216.165/mac/progmac/progmac.lat
Resolving download.ff.avast.com...
Resolved as 95.211.174.155
Downloading http://95.211.174.155/mac/progmac/progmac.lat...
Cannot download http://95.211.174.155/mac/progmac/progmac.lat
Resolving download.ff.avast.com...
Resolved as 208.43.153.4
Downloading http://208.43.153.4/mac/progmac/progmac.lat...
Cannot download http://208.43.153.4/mac/progmac/progmac.lat
Resolving download.ff.avast.com...
Resolved as 208.43.153.4
Downloading http://208.43.153.4/mac/progmac/progmac.lat...
Cannot download http://208.43.153.4/mac/progmac/progmac.lat
Resolving download.ff.avast.com...
Resolved as 95.211.174.155
Downloading http://95.211.174.155/mac/progmac/progmac.lat...
Cannot download http://95.211.174.155/mac/progmac/progmac.lat
Failed: cannot determine latest progmac version

There were 5 different addresses in the error log resolved for download.ff.avast.com.
Title: Re: Updater blocked
Post by: Kyowashiki on November 14, 2012, 02:51:46 AM
Dear Sirs

In Avast 7.0 (37781), update through proxy server is still not working on my iMac (late 2006, OS 10.7.5 (11G63)).  Proxy is configured for http, https, ftp, rtsp, and gopher but not for socks in our company. 

Error log is essentially the same as above described. 

Is there any way to edit the proxy server setting directly, to download virus definition directly, or to copy virus definition files from other machines. 

Sincerely.
Title: Re: Updater blocked
Post by: zilog on November 14, 2012, 01:55:37 PM
Dear Sirs

In Avast 7.0 (37781), update through proxy server is still not working on my iMac (late 2006, OS 10.7.5 (11G63)).  Proxy is configured for http, https, ftp, rtsp, and gopher but not for socks in our company. 

Error log is essentially the same as above described. 

Is there any way to edit the proxy server setting directly, to download virus definition directly, or to copy virus definition files from other machines. 

Sincerely.

Hallo,
in the fact, we support proxy though the environment variable "http_proxy". Unfortunatelty, MacOS doesn't propagate system preferences's state there, so it's up on the user.
More info here: http://fuzzy76.net/147/mac-os-x-tips/

regards,
pc
Title: Re: Updater blocked
Post by: Kyowashiki on November 21, 2012, 03:57:04 AM
Dear Sirs

Hallo,
in the fact, we support proxy though the environment variable "http_proxy". Unfortunatelty, MacOS doesn't propagate system preferences's state there, so it's up on the user.
More info here: http://fuzzy76.net/147/mac-os-x-tips/

regards,
pc

Thank you, zilog for the information.  Unfortunately it didn't help me.  I created ~/profile as described in http://fuzzy76.net/147/mac-os-x-tips/, and then edit sudoers.  In terminal bash said "etc/http_proxy; there is no such files or directory". 
Then I tried another way. 
I edit ~/.profile as
"export http_proxy=http://server name:8080
 export HTTP_PROXY=http://server name:8080"

In terminal, command "echo $http_proxy" returns "server name:8080", so environment variable "http_proxy" seemed to be set correctly.  But Avast show the same error log as before. 
Is there anything else to do?
Title: Re: Updater blocked
Post by: zilog on November 21, 2012, 05:07:06 PM
Dear Sirs

Hallo,
in the fact, we support proxy though the environment variable "http_proxy". Unfortunatelty, MacOS doesn't propagate system preferences's state there, so it's up on the user.
More info here: http://fuzzy76.net/147/mac-os-x-tips/

regards,
pc

Thank you, zilog for the information.  Unfortunately it didn't help me.  I created ~/profile as described in http://fuzzy76.net/147/mac-os-x-tips/, and then edit sudoers.  In terminal bash said "etc/http_proxy; there is no such files or directory". 
Then I tried another way. 
I edit ~/.profile as
"export http_proxy=http://server name:8080
 export HTTP_PROXY=http://server name:8080"

In terminal, command "echo $http_proxy" returns "server name:8080", so environment variable "http_proxy" seemed to be set correctly.  But Avast show the same error log as before. 
Is there anything else to do?
Hallo,
You must propagate this to the launchd-launched parts as well. ~/.profile affects only things that are started upon your login.
So, the proper place where to put this is probably system-wide launchd.conf - more info here: http://serverfault.com/questions/16355/how-to-set-global-path-on-os-x

Regards,
pc