Applications used within your network sometimes require specific configuration on Web Gateway / UTM in order for them to communicate with servers on the internet, etc. Please select the appropriate software from the menu on the right. Possible reasons for an application not working under the default configuration include:
- Application communicates using protocols other than HTTP or HTTPS: By default, most internet traffic is blocked unless it is HTTP or HTTPS. Applications using other protocols will usually require specific firewall rules to be added. If the application is not listed here, check the vendor's website for firewalling instructions. Beware of vendors who suggest opening large ranges of ports, or HTTP (80/tcp) or HTTPS (443/tcp) to non-specific IP addresses.
- Application communicates using HTTP/HTTPS but is being blocked: Check the web proxy logs to see if any of the application's traffic is being blocked by the web filter. If so, either exclude the addresses from the appropriate categories, or whitelist them. The Connectivity Warnings option on the Web Proxy -> Logs report is especially useful.
- Application sends nonstandard traffic over TCP ports 80 or 443: Traffic over TCP port 80 traffic to be HTTP and port 443 traffic is expected to be HTTPS. If an application is using these standard ports for a nonstandard protocol, specific rules must be added to the firewall to avoid this traffic being directed through the transparent proxy.
- Application is incompatible with HTTPS interception: If the application does not consult the device's standard certificate store, it may fail to make connections. Disable active HTTPS interception for the domains that it is accessing. Again, see the Connectivity Warnings option on the Web Proxy -> Logs report to identify this traffic.