Home Support

AVG Support Community

Share tips and solutions on AVG Products

Have a question?

Community topics

AVG Gurus

These community experts are here to help

  • (AB) Alan Binch
  • (BA) Borislav Angelov
  • (VB) Vladimir Bartl
  • (SK) Subhadeep Kanungo
  • (MS) Miloslav Serba
Ross CavuRoss Cavu 

Traffic to Meraki

Hello Community,
I'm new to AVG on Mac.   I downloaded the free version to quickly test whether this app will work for my small business. I am currently running into an issue where my my mac will not allow the Meraki client manager (it's an MDM solution) while AVG is installed (disabling it still causes traffic issues).  The MDM solution is not an app; it runs as a service / profile on my system, so I can't simply go to System Preferences > Firewall > Allow App.

Before I take the plunge on a license I'd like to know whether the AVG for Mac antivirus solution gives the ability to allow service traffic like this to pass through unencumbered.

-980888528-980888528 (Avast)
Hi Ross,

Let's try to look into this together.
If an AVG AntiVirus blocks any program or service, it should work once we disable AVG.
Since you already disabled AVG and there was some traffic issue, it could be possible that some other program may be interfering.
AVG for MAC doesn't have firewall so we do not have any rules to allow or block.
Please let me know if you get any message or error while accessing the MDM solution when AVG is enabled to proceed further.
Ross CavuRoss Cavu

Thank you Ranjani,

I've disabled, but the issue communicating to Meraki persists.  When I uninstall / delete AVG, the connection resumes. 

With AVG Mac Shield and Web Shield "turned off", the errors while I tail the logs are a loop of this:

2018-02-28 11:51:37.172618 [0x700003e97000]: TunClient::main() [pcc180.meraki.com:993], starting up...
2018-02-28 11:51:38.525397 [0x700003e97000]: check_cert(): !SSL_get_verify_result()
2018-02-28 11:51:38.525443 [0x700003e97000]: TunClient::connect_to_proxy(): warning: check_cert returned false!
2018-02-28 11:51:45.131109 [0x700003e97000]: check_cert(): !SSL_get_verify_result()
2018-02-28 11:51:45.131156 [0x700003e97000]: TunClient::connect_to_proxy(): warning: check_cert returned false!
When I uninstall AVG, this is the same log:
2018-02-28 11:55:42.671570 [0x700003e97000]: TunClient::handle_request [pcc180.meraki.com]: request 
2018-02-28 11:55:42.840366 [0x700003e97000]: TunClient::handle_request [pcc180.meraki.com]: request 
2018-02-28 11:55:43.336507 [0x700003e97000]: TunClient::handle_request [pcc180.meraki.com]: request 
2018-02-28 11:55:43.665403 [0x700003e97000]: TunClient::handle_request [pcc180.meraki.com]: request 
2018-02-28 11:55:43.837955 [0x700003e97000]: TunClient::handle_request [pcc180.meraki.com]: request

Ross CavuRoss Cavu


Any updates on this issue?  I did some research on my own, but as you mentioned, the AVG for Mac version doesn't have a Firewall portion.  On my end, I've updated the Mac Application Firewall to allow all traffic for Meraki and AVG. But the issue persists.  As long as AVG is installed, the errors appear and cause problems

-980888528-980888528 (Avast)
Thank you for waiting and for the log files, Ross.

It's not possible to whitelist such traffic at the moment so we don't recommend using AVG and "Meraki" together. Thank you for your understanding!
Ross CavuRoss Cavu


I understand that locally there isn't anything we can whitelist. I found there is precedence for this type of issue relating to Meraki and AVG traffic.  A support thread for a year ago (this one (https://support.avg.com/answers?id=906b0000000DYwBAAW)) has a user and support agent discussing the inability of AVG udating through their Meraki AMP.   

Could you escalate this issue?  Perhaps this meraki/avg communication issue could be addressed in future releases of AVG for Mac.

-980888528-980888528 (Avast)
Sure, Ross. I will escalate this case to our development team. Thank you for your valuable suggestion. 
Balasubramanian SBalasubramanian S (AVG) 
Hi Ross,

Thank you for being patient.
Your feedback was already passed to our product team.
However, we will not be able to guarantee whether it will be fixed.
Ross CavuRoss Cavu

Hello  Balasubramanian,
Thank you for the response. And I understand that there is no guarantee. 


Ask a question
Struggling with non-AVG technology? We can fix that, too!