Avast Web Shield - Blocking HTTP Traffic

[REDACTED]

Stunning own goal by Avast, auto update of Avast for Mac wiped out 3/4 of my internet traffic. Everything working on Yosemite, went on holiday for a week, stupidly left mac on and it updated. Little or no web access on my return

Spent all day looking at DNS and Proxy issues, even down to the wires. Was probably 20 mins away from a clean install, when finally tracked down to latest update. Switch of Web Shield and all traffic back.

Any chance we can get this fixed, ?

K

[tumic]

Any chance we can get this fixed, ?

Not until you provide a little bit more info... The system log would be a minimum, but usually
the whole support package (Help->Support->Create support package) is required.

[specimen9999]

Any chance we can get this fixed, ?

Not until you provide a little bit more info... The system log would be a minimum, but usually
the whole support package (Help->Support->Create support package) is required.

I'm glad I'm not the only one having this issue, but unfortunately in my case you played it down and didn't ask me to provide the package.

[specimen9999]

https://forum.avast.com/index.php?topic=158357.0

[tumic]

in my case you played it down and didn't ask me to provide the package.

No, I didn't. You have already included a relevant system log part in your post, so there was
no need to request the support package.

[specimen9999]

Happened again...

Code: [Select]

12/11/14 13:38:12,120 com.avast.proxy[18133]: SSL_get_verify_result(): <server address edited out>: self signed certificate
12/11/14 13:38:41,000 kernel[0]: Google Chrome He (map: 0xffffff803193ef00) triggered DYLD shared region unnest for map: 0xffffff803193ef00, region 0x7fff88000000->0x7fff88200000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
12/11/14 13:38:55,000 kernel[0]: Google Chrome He (map: 0xffffff8030e73780) triggered DYLD shared region unnest for map: 0xffffff8030e73780, region 0x7fff88000000->0x7fff88200000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
12/11/14 13:38:57,996 Google Chrome Helper[21201]: CoreText CopyFontsForRequest received mig IPC error (FFFFFFFFFFFFFECC) from font server
12/11/14 13:38:57,996 Google Chrome Helper[21201]: CoreText CopyFontsForRequest received mig IPC error (FFFFFFFFFFFFFECC) from font server
12/11/14 13:38:58,301 Google Chrome Helper[21201]: CoreText CopyFontsForRequest received mig IPC error (FFFFFFFFFFFFFECC) from font server
12/11/14 13:38:58,302 Google Chrome Helper[21201]: CoreText CopyFontsForRequest received mig IPC error (FFFFFFFFFFFFFECC) from font server
12/11/14 13:38:58,430 Google Chrome Helper[21201]: CoreText CopyFontsForRequest received mig IPC error (FFFFFFFFFFFFFECC) from font server
12/11/14 13:38:58,430 Google Chrome Helper[21201]: CoreText CopyFontsForRequest received mig IPC error (FFFFFFFFFFFFFECC) from font server
12/11/14 13:38:58,512 Google Chrome Helper[21201]: CoreText CopyFontsForRequest received mig IPC error (FFFFFFFFFFFFFECC) from font server
12/11/14 13:38:58,512 Google Chrome Helper[21201]: CoreText CopyFontsForRequest received mig IPC error (FFFFFFFFFFFFFECC) from font server
12/11/14 13:38:58,867 Google Chrome Helper[21201]: CoreText CopyFontsForRequest received mig IPC error (FFFFFFFFFFFFFECC) from font server
12/11/14 13:38:58,867 Google Chrome Helper[21201]: CoreText CopyFontsForRequest received mig IPC error (FFFFFFFFFFFFFECC) from font server
12/11/14 13:38:58,920 Google Chrome Helper[21201]: CoreText CopyFontsForRequest received mig IPC error (FFFFFFFFFFFFFECC) from font server
12/11/14 13:38:58,921 Google Chrome Helper[21201]: CoreText CopyFontsForRequest received mig IPC error (FFFFFFFFFFFFFECC) from font server
12/11/14 13:38:59,020 Google Chrome Helper[21201]: CoreText CopyFontsForRequest received mig IPC error (FFFFFFFFFFFFFECC) from font server
12/11/14 13:38:59,021 Google Chrome Helper[21201]: CoreText CopyFontsForRequest received mig IPC error (FFFFFFFFFFFFFECC) from font server
12/11/14 13:38:59,108 Google Chrome Helper[21201]: CoreText CopyFontsForRequest received mig IPC error (FFFFFFFFFFFFFECC) from font server
12/11/14 13:38:59,108 Google Chrome Helper[21201]: CoreText CopyFontsForRequest received mig IPC error (FFFFFFFFFFFFFECC) from font server
12/11/14 13:39:10,779 com.avast.proxy[18133]: SSL_get_verify_result(): <server address edited out>: self signed certificate
12/11/14 13:39:32,167 com.avast.proxy[18133]: SSL_get_verify_result(): <server address edited out>: self signed certificate
12/11/14 13:40:11,000 kernel[0]: Google Chrome He (map: 0xffffff80382175a0) triggered DYLD shared region unnest for map: 0xffffff80382175a0, region 0x7fff88000000->0x7fff88200000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
12/11/14 13:40:13,397 com.avast.proxy[18133]: SSL_get_verify_result(): <server address edited out>: self signed certificate
12/11/14 13:40:59,077 com.apple.SecurityServer[58]: Killing auth hosts
12/11/14 13:40:59,077 com.apple.SecurityServer[58]: Session 100206 destroyed
12/11/14 13:40:59,220 com.apple.SecurityServer[58]: Session 100248 created
12/11/14 13:40:59,257 Mail[18379]: CFNetwork SSLHandshake failed (-9806)

This is when I killed the process, com.avast.proxy
12/11/14 13:40:59,262 com.apple.xpc.launchd[1]: (com.avast.proxy[18133]) Service exited due to signal: Killed: 9
12/11/14 13:40:59,328 com.avast.proxy[21208]: Starting daemon.
12/11/14 13:41:01,740 com.avast.proxy[21208]: swquery.apple.com:https: nodename nor servname provided, or not known
12/11/14 13:41:09,985 Console[21212]: Failed to connect (_consoleX) outlet from (NSApplication) to (ConsoleX): missing setter or instance variable
12/11/14 13:41:39,762 Mail[18379]: CFNetwork SSLHandshake failed (-9806)

(I edited the log and removed the email server address that uses a self-signed certificate, for privacy reasons)

[tumic]

Hi,
There is a new beta version out there, that may fix this issue.