Watchman Monitoring generally does not require changes to firewalls and/or proxy servers for proper functionality. In a few instances, outbound traffic rules might require whitelisting. The following details the various access details that might be needed for your proxy server or firewall.
Inbound Access - Not required
The Monitoring Client agent accepts no incoming network traffic. Port forwarding or additional configuration is NOT required.
The Monitoring Client agent submits hourly reports via an https post via the standard port of 443. HTTPS is compatible with most firewalls and proxies.
Proxy Servers
The hourly HTTPS submission of the Monitoring Client agent is compatible the majority of proxy-servers.
There is currently no support for authenticated proxies.
Outbound Traffic Rules
The following settings are required for manual creation of an outbound traffic rule or whitelisting.
The Monitoring Client agent will use the system DNS configuration to resolve the reporting server.
*.monitoringclient.comThe IP Addresses to whitelist include:
54.245.108.65
54.245.108.121
54.245.99.155
54.245.99.156The report is submitted to port 443 of the Watchman Monitoring server.
Separate rules for auto-updating
The auto-update process relies on a separate validation server, and access to Amazon's S3 network.
mc-mac-installers-production.s3.amazonaws.comAdblockers and the Dashboard
Adblockers, such as uBlock, may block portions of the Watchman Monitoring Dashboard interface. We highly recommend whitelisting *.monitoringclient.com . The following domains should be whitelisted with your adblocker for the best functionality of the Dashboard.
*.monitoringclient.com
monitoringclient.s3.amazonaws.com
zdassets.com
zendesk.com
livechatinc.comPermalink: https://www.watchmanmonitoring.com/firewall
How can this article be improved?
Please sign in to leave a comment.