Interesting I have had my first problem with the beta, though I'm not sure if it is the beta, possibly the new tweaking of the update function, but an auto update failed (with cannot connect Red Pop-up). This is the first time this has happened (outside of my disconnecting the dial-up whilst an update check is in process
Information about current update:
Last encountered error: Cannot connect to www2[break].avast.com (195.47.75.56:80).
Total time: 5:39
I noticed the www2 difference in the URL as possibly the only difference. I checked the servers.def file and see that these are (external beta) servers.
I have tried a manual update and I'm sat watching my firewall logs as avast.setup (not blocked) cycles through the servers.def URLs as it fails trying to download servers.def.vpu
I'm also seeing the remote address as cat.asw.cz I assume that is where the beta servers are, which begs the question why is the domain shown as www2 . avast.com ?
I can only assume this is the beta update issue that you have been chasing, as:
1. I am connected to the internet.
2. avast.setup is allowed and in the outbound firewall log.
3. there is no http proxy.
4. which only leaves - the server is inaccessible because of a network error or maintenance.
See attached error log avastUpdErr.txt file.