[MAC] Firewall notification pops up after every reboot

Discussion in 'Quality Control' started by saturnotaku, Jan 12, 2015.

  1. saturnotaku

    saturnotaku Beta Tester

    Joined:
    Jan 9, 2015
    Messages:
    55
    See the following screenshot for a message that pops up every time I reboot my system and have Adguard set to launch at startup. This message comes from the built-in OS X firewall, which I have enabled. If the firewall is disabled, the message does not appear.

    Adguard 1.0.36 beta and OS X Yosemite 10.10.1.
     

    Attached Files:

  2. avatar

    avatar Administrator Staff Member Administrator

    Joined:
    Oct 26, 2010
    Messages:
    13,135
    Could you please show a screenshot with your firewall settings?
     
  3. saturnotaku

    saturnotaku Beta Tester

    Joined:
    Jan 9, 2015
    Messages:
    55
    Here you go.
     

    Attached Files:

  4. Boo Berry

    Boo Berry Moderator + Beta Tester Moderator

    Joined:
    May 30, 2012
    Messages:
    3,794
    Does Adguard use a valid certificate? If so, this *may* workaround these type of issues (and potential issues with Gatekeeper too). I haven't had time to check.
     
  5. avatar

    avatar Administrator Staff Member Administrator

    Joined:
    Oct 26, 2010
    Messages:
    13,135
    Yes we do, even two certs, one for app and second for kernel extension.
     
  6. saturnotaku

    saturnotaku Beta Tester

    Joined:
    Jan 9, 2015
    Messages:
    55
    Steam had the same issue last month where the firewall notification would pop up every time the program launched. They were able to fix it, so I have to imagine it will be the same for Adguard.
     
  7. vasily_bagirov

    vasily_bagirov Administrator Staff Member Administrator

    Joined:
    Jul 1, 2014
    Messages:
    6,902
    This should no more be a problem with a new beta update we released today. Hope it helps!
     
  8. saturnotaku

    saturnotaku Beta Tester

    Joined:
    Jan 9, 2015
    Messages:
    55
    I will update when I get home. Appreciate the fast turnaround.
     
  9. saturnotaku

    saturnotaku Beta Tester

    Joined:
    Jan 9, 2015
    Messages:
    55
    1.0.37 beta did not fix the firewall pop-up appearing after every restart. It also appears to have broken the ability to block ads on Youtube. In the older beta and with the browser extension, the ad at the top of the page, as shown in the screenshot, is properly blocked. This happens in both Chrome and Safari. Also, the little Adguard assistant icon does not appear in the lower right corner of either browser.

    Edit: Reinstalled 1.0.36 and all is back to normal, save for, of course, the issue with the firewall notification appearing after reboot.

    Also, is it OK to have the browser extension installed concurrently with the software? It seems that having one defeats the purpose of the other. Just curious.
     

    Attached Files:

    Last edited by a moderator: Jan 15, 2015
  10. Boo Berry

    Boo Berry Moderator + Beta Tester Moderator

    Joined:
    May 30, 2012
    Messages:
    3,794
    Oh boy, I hope the HTTPS issue didn't creep into the Mac version.
     
  11. saturnotaku

    saturnotaku Beta Tester

    Joined:
    Jan 9, 2015
    Messages:
    55
    It must have because I added SeaMonkey as a filtered application (this browser is not filtered by default), and no HTTPS sites work as a result.
     
  12. avatar

    avatar Administrator Staff Member Administrator

    Joined:
    Oct 26, 2010
    Messages:
    13,135
  13. avatar

    avatar Administrator Staff Member Administrator

    Joined:
    Oct 26, 2010
    Messages:
    13,135
    This youtube issue is now fixed in 1.0.39.
     
  14. saturnotaku

    saturnotaku Beta Tester

    Joined:
    Jan 9, 2015
    Messages:
    55
    It is, however, the firewall popup issue is still present. See attached.
     

    Attached Files:

  15. vasily_bagirov

    vasily_bagirov Administrator Staff Member Administrator

    Joined:
    Jul 1, 2014
    Messages:
    6,902
    Thanks for reminder, we are aware of this, and working on the fix atm.