Category:Third Party Software Compatibility

Applications used within your network sometimes require specific configuration on the Opendium system in order for them to communicate with servers on the internet, etc. Please select the appropriate software from the list below. 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 or 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.
• Application sends non-standard traffic over TCP ports 80 or 443: Traffic over TCP port 80 is expected to be HTTP and port 443 traffic is expected to be HTTPS. If an application is using these standard ports for a non-standard protocol, specific rules must be added to the firewall to avoid this traffic being directed through the transparent proxy.
• Application is incompatible with HTTPS decryption: If the application does not consult the device's standard certificate store, it may fail to make connections. Disable active HTTPS decryption for the domains that it is accessing. Using the Web Logs report with Filter status set to Connectivity Problems can be helpful to identify this traffic. However, beware that it is normal for a lot of legitimate traffic to be listed in this report as well, so blindly turning off decryption for the domains in the report is a very bad idea.