Author Topic: Can't connect to internet with Web Shield enabled  (Read 8096 times)

0 Members and 1 Guest are viewing this topic.

Offline mrebhun

  • Newbie
  • *
  • Posts: 5
Can't connect to internet with Web Shield enabled
« on: May 19, 2015, 07:42:14 PM »
New to Avast  Installed program yesterday.  Ran virus scan and except for being unable to scan 4 items no issues.  This morning, when I logged on, unable to connect to the internet.  I have reset the modem and restarted the computer.  If I disable Web Shield I can connect just fine.  I get the following error message with Web Shield enabled:
Safari can't open the page
"https://www.google.com/?gws_rd=ssl" because Safari can't establish a secure connection to the server "www.google.com"

I have tried other connections, like Yahoo, but same issue with different problems.  I did delete secure line VPN which seemed to make no difference either way since I didn't want that program.

Any ideas?

Need to add free version on a Mac
Modify message

Offline mrebhun

  • Newbie
  • *
  • Posts: 5
Re: Can't connect to internet with Web Shield enabled
« Reply #1 on: May 19, 2015, 09:00:12 PM »
I did find another temp fix.  Per another thread here I disabled the Scan Secured Connections block on the WebShield preference section and that seems to have helped but not feeling too good about leaving this unchecked.  I at least can run WebShield but obviously not fully.  I have upgraded to OS X 10.10.3 and I did remove Avast and reinstall.  Program information tells me I have version 10.14.

Offline tumic

  • Moderator
  • Advanced Poster
  • *
  • Posts: 724
Re: Can't connect to internet with Web Shield enabled
« Reply #2 on: May 20, 2015, 11:57:05 AM »
Please attach the relevant system log file parts, otherwise there is nothing we can do about the issue.

Offline mrebhun

  • Newbie
  • *
  • Posts: 5
Re: Can't connect to internet with Web Shield enabled
« Reply #3 on: May 20, 2015, 02:38:49 PM »
I am a long time PC user but new to Mac.  Where do I find the files you need.

Marc

Offline mrebhun

  • Newbie
  • *
  • Posts: 5
Re: Can't connect to internet with Web Shield enabled
« Reply #4 on: May 21, 2015, 07:25:37 PM »
Here is today's system log file for Avast.  If not what you need you are going to have to help me out here
Date/Time:       2015-05-21 13:09:58 -0400
OS Version:      10.10.3 (Build 14D136)
Architecture:    x86_64h
Report Version:  21

Command:         Avast Mac Security
Path:            /Applications/Avast.app/Contents/MacOS/Avast
Version:         10.14 (44414)
PID:             652

Event:           spin-lite
Duration:        5.10s (process was unresponsive for 2 seconds before sampling)
Steps:           52 (100ms sampling interval)

Hardware model:  iMac14,1
Active cpus:     4

Fan speed:       1402 rpm

Heaviest stack for the main thread of the target process:
  52  start + 52 (Avast + 8228) [0x100002024]
  52  NSApplicationMain + 1832 (AppKit + 13140) [0x7fff92ea6354]
  52  -[NSApplication run] + 594 (AppKit + 551923) [0x7fff92f29bf3]
  52  -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 346 (AppKit + 593768) [0x7fff92f33f68]
  52  _DPSNextEvent + 978 (AppKit + 596411) [0x7fff92f349bb]
  52  _BlockUntilNextEventMatchingListInModeWithFilter + 71 (HIToolbox + 205099) [0x7fff8d5e312b]
  52  ReceiveNextEventCommon + 431 (HIToolbox + 205546) [0x7fff8d5e32ea]
  52  RunCurrentEventLoopInMode + 235 (HIToolbox + 206191) [0x7fff8d5e356f]
  52  CFRunLoopRunSpecific + 296 (CoreFoundation + 465880) [0x7fff94c38bd8]
  52  __CFRunLoopRun + 2024 (CoreFoundation + 468488) [0x7fff94c39608]
  52  __CFRunLoopDoTimers + 301 (CoreFoundation + 1221949) [0x7fff94cf153d]
  52  __CFRunLoopDoTimer + 1059 (CoreFoundation + 749427) [0x7fff94c7df73]
  52  __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 20 (CoreFoundation + 750308) [0x7fff94c7e2e4]
  52  WebCore::timerFired(__CFRunLoopTimer*, void*) + 20 (WebCore + 127588) [0x7fff867f4264]
  52  WebCore::ThreadTimers::sharedTimerFiredInternal() + 157 (WebCore + 127805) [0x7fff867f433d]
  52  WebCore::DOMTimer::fired() + 297 (WebCore + 1684041) [0x7fff86970249]
  52  WebCore::ScheduledAction::execute(WebCore::Document*) + 141 (WebCore + 1684493) [0x7fff8697040d]
  52  WebCore::ScheduledAction::executeFunctionInContext(JSC::JSGlobalObject*, JSC::JSValue, WebCore::ScriptExecutionContext*) + 537 (WebCore + 1685145) [0x7fff86970699]
  52  JSC::call(JSC::ExecState*, JSC::JSValue, JSC::CallType, JSC::CallData const&, JSC::JSValue, JSC::ArgList const&, JSC::JSValue*) + 63 (JavaScriptCore + 2321311) [0x7fff8c44fb9f]
  52  JSC::Interpreter::executeCall(JSC::ExecState*, JSC::JSObject*, JSC::CallType, JSC::CallData const&, JSC::JSValue, JSC::ArgList const&) + 462 (JavaScriptCore + 397502) [0x7fff8c27a0be]
  52  JSC::JITCode::execute(JSC::VM*, JSC::ProtoCallFrame*) + 35 (JavaScriptCore + 3790307) [0x7fff8c5b65e3]
  52  callToJavaScript + 311 (JavaScriptCore + 4297873) [0x7fff8c632491]
  52  llint_entry + 22764 (JavaScriptCore + 4321186) [0x7fff8c637fa2]
  52  llint_entry + 22753 (JavaScriptCore + 4321175) [0x7fff8c637f97]
  52  JSC::LLInt::setUpCall(JSC::ExecState*, JSC::Instruction*, JSC::CodeSpecializationKind, JSC::JSValue, JSC::LLIntCallLinkInfo*) + 452 (JavaScriptCore + 386004) [0x7fff8c2773d4]
  52  JSC::callRuntimeMethod(JSC::ExecState*) + 274 (WebCore + 12893122) [0x7fff87420bc2]
  52  JSC::Bindings::ObjcInstance::invokeMethod(JSC::ExecState*, JSC::RuntimeMethod*) + 191 (WebCore + 11523887) [0x7fff872d272f]
  52  JSC::Bindings::ObjcInstance::invokeObjcMethod(JSC::ExecState*, JSC::Bindings::ObjcMethod*) + 1082 (WebCore + 11525050) [0x7fff872d2bba]
  52  -[NSInvocation invoke] + 290 (CoreFoundation + 243218) [0x7fff94c02612]
  52  __invoking___ + 140 (CoreFoundation + 243644) [0x7fff94c027bc]
  52  -[Avastium pairWithCallback:params:] + 545 (Avast + 381985) [0x10005d421]
  52  -[AvastAccountModel pairWithSessionId:email:localeLid:completionHandler:] + 889 (Avast + 519769) [0x10007ee59]
  52  -[AVCCService privilegedSocket] + 303 (Avast + 619871) [0x10009755f]
  51  submitOnDemandJob + 108 (Avast + 471228) [0x1000730bc]
  51  AuthorizationCreate + 151 (Security + 740599) [0x7fff8ec31cf7]
  51  xpc_connection_send_message_with_reply_sync + 200 (libxpc.dylib + 32221) [0x7fff8be68ddd]
  51  semaphore_wait_trap + 10 (libsystem_kernel.dylib + 70938) [0x7fff9025451a]
 *51  semaphore_wait_continue + 0 (kernel + 1357760) [0xffffff800034b7c0]

  Binary Images:
         0x100000000 -        0x1000f7fff  com.avast.AAFM 10.14 (44414)                <B7047E51-3E37-3A6B-8179-936CBE4CAD33>  /Applications/Avast.app/Contents/MacOS/Avast
      0x7fff867d5000 -     0x7fff87797fff  com.apple.WebCore 10600 (10600.5.17)        <587F71B3-28E7-3EBC-87B3-1F5E1D8C1349>  /System/Library/Frameworks/WebKit.framework/Versions/A/Frameworks/WebCore.framework/Versions/A/WebCore
      0x7fff8be61000 -     0x7fff8be89fff  libxpc.dylib (559.20.9)                     <D35D0DB2-D7BD-3BE4-8378-062BFE545E1D>  /usr/lib/system/libxpc.dylib
      0x7fff8c219000 -     0x7fff8c72efff  com.apple.JavaScriptCore 10600 (10600.5.10) <ED4CABC6-0952-3E28-A3CD-32CA5CE22252>  /System/Library/Frameworks/JavaScriptCore.framework/Versions/A/JavaScriptCore
      0x7fff8d5b1000 -     0x7fff8d8b6fff  com.apple.HIToolbox 2.1.1 (758.7)           <6711FAA9-904A-3B49-9665-FC8D13B93C42>  /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox
      0x7fff8eb7d000 -     0x7fff8ede7fff  com.apple.security 7.0 (57031.20.26)        <6568520A-587D-3167-BB79-60CE6FEADC64>  /System/Library/Frameworks/Security.framework/Versions/A/Security
      0x7fff90243000 -     0x7fff90260fff  libsystem_kernel.dylib (2782.20.48)         <EAFD7BD0-0C30-3E7D-9528-F9916BA0167C>  /usr/lib/system/libsystem_kernel.dylib
      0x7fff92ea3000 -     0x7fff93a24fff  com.apple.AppKit 6.9 (1347.57)              <B214D528-7D1C-39B2-BE36-821D417A0297>  /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
      0x7fff94bc7000 -     0x7fff94f5ffff  com.apple.CoreFoundation 6.9 (1153.18)      <5C0892B8-9691-341F-9279-CA3A74D59AA0>  /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
 *0xffffff8000200000 - 0xffffff80009fffff  kernel (2782.20.48)                         <4B3A11F4-77AA-3D27-A22D-81A1BC5B504D>  /System/Library/Kernels/kernel
 

Offline mrebhun

  • Newbie
  • *
  • Posts: 5
Re: Can't connect to internet with Web Shield enabled
« Reply #5 on: May 24, 2015, 09:49:05 PM »
Well, by now, becoming evident to me no one willing to help.  At least the program was free.

Thanks

Marc

Offline booterror1973

  • Newbie
  • *
  • Posts: 2
Re: Can't connect to internet with Web Shield enabled
« Reply #6 on: June 09, 2015, 10:38:49 PM »
Also started today to have the same problem with web shield , all the secure (https) sites etc. where not working.
Took some time to figure out that Avast was the culprit.

I am running OSx El Capitan on MacBookPro Late 2011.

Offline heelsfan7j

  • Newbie
  • *
  • Posts: 1
Re: Can't connect to internet with Web Shield enabled
« Reply #7 on: June 20, 2015, 06:44:36 AM »
Had the same problem.  Downloaded Avast on my Mac and suddenly could not access Google, AOL, or Yahoo.  Oddly enough, I could access MSN.com when I tested it, but then tried to fun a search from that page and no other web pages would come up.  Wanted to search for a suggested fix for Avast shutting down access to virtually all websites, but couldn't get to just about anywhere on the Internet.  Disabled Web Shield and now I can access everything again.

I like Avast, but if I have to leave Web Shield turned off all of the time, it defeats the purpose of having it.  It appears I am not the only one with this issue, so please look into it. 

Offline specimen9999

  • Sr. Member
  • ****
  • Posts: 349
Re: Can't connect to internet with Web Shield enabled
« Reply #8 on: June 20, 2015, 03:14:39 PM »
Don't disable the webshield, just disable the option to scan secured connections. Which in my view shouldn't even be enabled because of the mechanism it uses to be able to do this (it's a benevolent MITM 'attack', it uncrypts the data, scans and then encrypts again using an avast cert).
« Last Edit: June 20, 2015, 03:19:45 PM by specimen9999 »

Offline darkpower_4

  • Newbie
  • *
  • Posts: 1
Re: Can't connect to internet with Web Shield enabled
« Reply #9 on: June 20, 2015, 08:02:42 PM »
same problem...its my wifes computer and i argued that it wasnt avast with her for twenty minutes finally just uninstalled it thinking it would still do it but it didnt anymore now i look like an idiot ive been using avast for years on my windows computer and android phone but now im not happy and she doesnt want to use it anymore telling me macs dont get viruses anyway (mac delusion) she thinks she is right and doesnt want antivirus and if i try to tell her otherwise she wants to go to the store and by norton! you guys better fix this. it happened after upgrading to 10.10 osx. This is making me a very unhappy avast user.

Offline booterror1973

  • Newbie
  • *
  • Posts: 2
Re: Can't connect to internet with Web Shield enabled
« Reply #10 on: June 21, 2015, 08:19:00 PM »
My solution is just to uninstall Avast....they are not bothered enough to fix it, it seems.
It was not only the HTTPS sites, but even the file check on my harddisk was messing up everything like keychain access etc.

Pity

Offline stevegoldfield

  • Newbie
  • *
  • Posts: 9
Re: Can't connect to internet with Web Shield enabled
« Reply #11 on: June 22, 2015, 06:06:31 PM »
I had and still have a similar but more specific problem. I was unable to connect to Fidelity or to my bank account with Web Shield on. Avast gave a spurious message about the certificate of the sites. Fidelity tech support told me that this was a widespread issue with Avast for OSX, that Avast was insisting on a new form of digital certificates which are not required until 2016. I was able to create an exception for Fidelity but not for my bank. There was a button to do so for Fidelity but not for my bank. I logged a ticket with Avast, but they essentially denied that they have a problem (which is ridiculous) and did nothing even after I tried to escalate the ticket. I still have to turn off web shield to login to my bank account. I have Avast premier installed on my Windows 7 laptop, and I never had this problem there.

Offline specimen9999

  • Sr. Member
  • ****
  • Posts: 349
Re: Can't connect to internet with Web Shield enabled
« Reply #12 on: June 22, 2015, 10:15:24 PM »
I had and still have a similar but more specific problem. I was unable to connect to Fidelity or to my bank account with Web Shield on. Avast gave a spurious message about the certificate of the sites. Fidelity tech support told me that this was a widespread issue with Avast for OSX, that Avast was insisting on a new form of digital certificates which are not required until 2016. I was able to create an exception for Fidelity but not for my bank. There was a button to do so for Fidelity but not for my bank. I logged a ticket with Avast, but they essentially denied that they have a problem (which is ridiculous) and did nothing even after I tried to escalate the ticket. I still have to turn off web shield to login to my bank account. I have Avast premier installed on my Windows 7 laptop, and I never had this problem there.

Didn't you read my comment about disabling https scan and not the webshield?

Offline dsstdf

  • Newbie
  • *
  • Posts: 8
Re: Can't connect to internet with Web Shield enabled
« Reply #13 on: June 29, 2015, 03:12:34 PM »
Not just a Mac issue.  I had the same problem with a fresh install on Windows.