In order for the AppsAnywhere Analytics server to operate, there are a number of inbound and outbound communications that must be enabled. The Analytics server itself will restrict these communications accordingly using its own, internal firewall, however they are documented here for informational purposes.

In this article

Also in this section

There are no sub-sections to this page


It is recommended that Analytics servers are provisioned on an internal network unless access to Analytics Dashboards is explicitly required via external connections.

All connections to the Analytics server should be blocked by an internal network firewall apart from the ones specified here. This article details all of the connections, inbound and outbound, that Analytics Server will need to make as part of it's general operations. 

Connectivity Requirements (Firewall Rules)

You will need to ensure that your network and firewalls are configured to permit the required traffic to and from your Analytics server.  The following tables detail the connectivity required, grouped according to the origin of the network traffic.

Internal Destinations should be amended to match your internal servers and services.

You do not need to configure any firewall rules on the Analytics server itself, as the virtual appliance is preconfigured with the required firewall rules.

Inbound Traffic (Internal)


Internal Destination



Analytics Viewer/Explorer (end user) devices analytics.uni.edu9999 TCPRetrieving content to be embedded into AppsAnywhere Analytics user interface and is required from all Analytics Viewer/Explorer (end user) devices (note: this is only the named Analytics Viewers/Explorers users and not all users of AppsAnywhere)
AppsAnywhere Serversanalytics.uni.edu19999 TCPAuthorizing sessions for AppsAnywhere Analytics and pulling data on behalf of AppsAnywhere Analytics UI and is only required from the AppsAnywhere Servers
Software2 Remote Access via VPN or Windows Jumphostanalytics.uni.edu22 TCPSoftware2 remote support for installation, configuration and upgrades

Outbound Traffic (Internal)


Internal Destination



Analytics ServerMSSQL.uni.edu1433 TCPConnection to your SQL database
Analytics ServerMSSQL.uni.edu1434 UDPConnection to your SQL database

Outbound Traffic (External)


Analytics Server

123 UDP

CentOS (Chrony) Time Service

Analytics Server

443 TCP

Appliance ACC, Daily License Check and CentOS updates

Analytics Server80 TCPCentOS updates

Analytics Server

587 TCP

Email alerts via SMTP

External Destinations

Optionally, you may wish to apply more specific firewall rules for outbound connections from your Analytics server.

The following table provides details of all the outbound destinations that Analytics requires access to during normal operation.

SourceExternal DestinationPortUsage
Analytics Server0.centos.pool.ntp.org123 UDPCentOS Time Service
Analytics Server1.centos.pool.ntp.org123 UDPCentOS Time Service
Analytics Server2.centos.pool.ntp.org123 UDPCentOS Time Service
Analytics Server3.centos.pool.ntp.org123 UDPCentOS Time Service
Analytics Servermirrorlist.centos.org80 TCPCentOS Update Repository
Analytics Servercdn.remirepo.net80 TCPCentOS Update Repository
Analytics Serverrpms.remirepo.net443 TCPCentOS Update Repository
Analytics TCPACC Updates
Analytics Serversoftware2-public.azureedge.net443 TCPACC Updates
Analytics Serverbitbucket.org443 TCPAnalytics model and ML updates used by reports and the reporting schema
Analytics Serverlicense.looker.com443 TCPDaily heartbeat to licensing server
Analytics Serversmtp.sendgrid.net587 TCPEmail alerts via SMTP

Some other articles you might find useful:

Written By: