Author Topic: com.avast.proxy blocking non-SSL connections  (Read 6491 times)

0 Members and 1 Guest are viewing this topic.

Offline specimen9999

  • Sr. Member
  • ****
  • Posts: 349
com.avast.proxy blocking non-SSL connections
« on: October 28, 2014, 04:32:47 PM »
OS X Yosemite
Avast Mac Security 2015

I have scan secured connections disabled for the Web Shield.

It has happened on more than one occasion that I cannot load a web page on Chrome or Safari, get any content from the web via curl or ping any web server via terminal.app until I force quit com.avast.proxy or disable and then re-enable the Web Shield, then all web connections work normally again.

As far as Console messages I only found these, that might or might not be relevant:

Code: [Select]
28/10/14 15:13:23,491 com.apple.xpc.launchd[1]: (com.avast.gui.privilegedHelper29807) This key does not do anything: OnDemand
28/10/14 15:13:23,491 com.apple.xpc.launchd[1]: (com.avast.gui.privilegedHelper29807) The ServiceIPC key is no longer respected. Please remove it.
28/10/14 15:13:23,687 com.avast.proxy[14670]: SIGHUP received. Reloading...
28/10/14 15:13:23,688 Mail[1811]: CFNetwork SSLHandshake failed (-9806)
28/10/14 15:13:25,902 com.avast.proxy[14670]: swquery.apple.com:https: nodename nor servname provided, or not known
28/10/14 15:13:26,448 com.avast.proxy[14670]: direct connection: 173.194.45.129:80
28/10/14 15:13:43,776 com.avast.proxy[14670]: SIGHUP received. Reloading...
28/10/14 15:13:43,779 Mail[1811]: CFNetwork SSLHandshake failed (-9806)
28/10/14 15:13:44,054 com.avast.proxy[14670]: swquery.apple.com:https: nodename nor servname provided, or not known
28/10/14 15:13:44,096 com.avast.proxy[14670]: direct connection: 74.125.206.109:993
...
28/10/14 15:14:14,515 com.avast.proxy[14670]: SIGHUP received. Reloading...
28/10/14 15:14:14,535 com.avast.service[13913]: BufConn::write: write() failed. Broken pipe [32]
28/10/14 15:14:15,088 com.avast.proxy[14670]: swquery.apple.com:https: nodename nor servname provided, or not known
28/10/14 15:14:15,516 com.avast.proxy[14670]: SIGHUP received. Reloading...
28/10/14 15:14:15,541 com.avast.service[13913]: BufConn::write: write() failed. Broken pipe [32]
28/10/14 15:14:15,541 com.avast.proxy[14670]: swquery.apple.com:https: nodename nor servname provided, or not known
28/10/14 15:14:19,861 com.avast.service[13913]: BufConn::write: write() failed. Broken pipe [32]
28/10/14 15:14:19,862 com.avast.service[13913]: BufConn::write: write() failed. Broken pipe [32]

Offline specimen9999

  • Sr. Member
  • ****
  • Posts: 349
Re: com.avast.proxy blocking non-SSL connections
« Reply #1 on: October 28, 2014, 04:37:51 PM »
I'm sorry for the double post, but unfortunately I cannot the delete the 2nd post and there's something wrong with the 'Post' functionality of the forum, as in, I never received a confirmation the post was made.

Offline DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 88900
  • No support PMs thanks
Re: com.avast.proxy blocking non-SSL connections
« Reply #2 on: October 28, 2014, 04:39:43 PM »
This is a forum bug - your duplicate has been removed.

I don't know about the notification issue as that is a function I don't use.
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 24.2.6105 (build 24.2.8918.824) UI 1.0.799/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

Offline specimen9999

  • Sr. Member
  • ****
  • Posts: 349
Re: com.avast.proxy blocking non-SSL connections
« Reply #3 on: October 28, 2014, 05:17:24 PM »
This is a forum bug - your duplicate has been removed.

I don't know about the notification issue as that is a function I don't use.

Thank you!

By confirmation I meant then when I clicked 'Post' the window did not refresh and the wheel kept spinning on Chrome, this happened 2 times in a row.

Offline DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 88900
  • No support PMs thanks
Re: com.avast.proxy blocking non-SSL connections
« Reply #4 on: October 28, 2014, 06:11:10 PM »
This is a forum bug - your duplicate has been removed.

I don't know about the notification issue as that is a function I don't use.

Thank you!

By confirmation I meant then when I clicked 'Post' the window did not refresh and the wheel kept spinning on Chrome, this happened 2 times in a row.

Yes, by all accounts it is this delay in completing the post that either triggers a repeat of the post or the user reposts as they don't think it has been sent.
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 24.2.6105 (build 24.2.8918.824) UI 1.0.799/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

Offline specimen9999

  • Sr. Member
  • ****
  • Posts: 349
Re: com.avast.proxy blocking non-SSL connections
« Reply #5 on: October 31, 2014, 11:13:41 PM »
*bump*

Offline tumic

  • Avast team
  • Advanced Poster
  • *
  • Posts: 723
Re: com.avast.proxy blocking non-SSL connections
« Reply #6 on: November 01, 2014, 11:18:47 AM »
According to the symptoms, this must be an issue in the packet redirection kernel module used by the proxy. But since we did not do any changes in the module for ages I guess it must have something to do with changes on your system - new OS version, new kernel module, etc. Anyway, until we are able to reproduce the issue, there is nothing we can do about it.

Offline specimen9999

  • Sr. Member
  • ****
  • Posts: 349
Re: com.avast.proxy blocking non-SSL connections
« Reply #7 on: November 01, 2014, 11:15:41 PM »
What I did was upgrading to Yosemite.

I have since reinstalled Yosemite on top of Yosemite, and I haven't seen this problem again, at least, yet, I didn't do this because of avast, but because of graphic performance issues.
« Last Edit: November 01, 2014, 11:18:04 PM by specimen9999 »

Offline specimen9999

  • Sr. Member
  • ****
  • Posts: 349
Re: com.avast.proxy blocking non-SSL connections
« Reply #8 on: November 08, 2014, 01:51:44 PM »
*sigh*

This has happened again.

And it's very frustrating, as I spent a lot of time flushing caches and confused why I could browse the internet normally on the iPad (non-SSL) and not on the Mac in the same network, had forgotten completely about this BUG with avast.proxy.
« Last Edit: November 08, 2014, 02:09:08 PM by specimen9999 »

Offline tumic

  • Avast team
  • Advanced Poster
  • *
  • Posts: 723
Re: com.avast.proxy blocking non-SSL connections
« Reply #9 on: November 27, 2014, 08:14:00 PM »
Hi,
there is a new beta version out there, that may fix this issue.

Offline specimen9999

  • Sr. Member
  • ****
  • Posts: 349
Re: com.avast.proxy blocking non-SSL connections
« Reply #10 on: November 27, 2014, 09:45:27 PM »
Hi,
there is a new beta version out there, that may fix this issue.

Thank you tumic, checked the beta channel and now running version 10.1 (43259), I'll report back if there's any issue.