robt7676

Reactions

0 Promote 0 Like 0 Boom 0 LOL 0 Spam 0 Abuse

Comments

  • Ah, good point.
    in HTTPS proxy deny message Comment by robt7676 November 7
  • There's actually a simple solution. Clone the proxy firewall policy and activate application control on only one and place it below the other with it deactivated. This way, the rule with WebBlocker will get hit first and the one below will catch anything else.
    in HTTPS proxy deny message Comment by robt7676 November 7
  • Thanks. Is there a reason why application control would see something like accessing protonvpn.com via a web browser as an application? It appears that's why it throws a DNS error rather than block page. If I turn off application control, it gets inspected and denied properly as a web page. As for NordVPN, I will reach out…
    in HTTPS proxy deny message Comment by robt7676 November 6
  • Some more information. It appears from the logs that in some caes, it's identifying the browser traffic as an application which makes no sense, but does explain why protonvpn.com simply wouldn't load. Even stranger is nordvpn.com loads even though the logs are saying it was denied.
    in HTTPS proxy deny message Comment by robt7676 November 6
  • Hi Bruce. I have it partially working, but it isn't consistent. For example, I have "Proxy Avoidance" as deny in the Default WebBlocker list and marked inspect in the AllowAll list. Here are the results when visiting specific pages: https://protonvpn.com shows a DNS error so doesn't load https://mullvad.net shows block…
    in HTTPS proxy deny message Comment by robt7676 November 6
  • Hi, new WatchGuard user here. Any chance you can post screenshots of the working configuration? Everything else was pretty straightforward to setup on the FireBox, but this particular item has me stumped. I have done the following: -Setup two WebBlocker lists ("Default" with items denied and "AllowAll" with nothing denied)…
    in HTTPS proxy deny message Comment by robt7676 November 6