Ports and Hostnames used for SiteWorx Gateway Connection

Updated by Dan Buckley

Ports

Gateways must be able to connect to reliable high-speed internet, with outbound firewall access to the following standard ports:

  • 443 (HTTPS - TCP): Secure HTTP, used for SiteWorx core services
  • 8444 (WAMP TCP): Web Application Messaging Protocol, used for SiteWorx core services
  • 123 (NTP - UDP): Network Time Protocol, used for synchronizing time between sensors and SiteWorx
  • 6514 (syslog over TLS - TCP): Secure Syslog used for SiteWorx logging and diagnostics
  • 53 (DNS - TCP): Domain Name Server, used for DNS lookup

FQDN

If the firewall configuration supports whitelisting fully qualified domain names (FQDN), SiteWorx recommends white-listing the following:

  • logs-01.loggly.com:6514
  • gateway3-images.s3.amazonaws.com:443
  • setup.siteworx.io:443
  • setup.siteworx.io:8444
  • <organization>-backend.siteworx.io:443
  • <organization>-backend.siteworx.io:8444

<organization> will be reliant on the first portion of the SiteWorx Custom URL (organization.siteworx.io). For example, gateways associated with the URL https://acmecorporation.siteworx.io will connect to acmecorporation-backend.siteworx.io:443 and acmecorporation-backend.siteworx.io:8444.

NTP

Gateways require NTP in order to authenticate with SiteWorx services. Gateways default to the following sequence of NTP servers:

  1. NTP server manually configured to gateway using Commissioner software (typically only used in static IP configurations)
  2. NTP server specified by DHCP server
  3. 0.digitallumens.pool.ntp.org, 1.digitallumens.pool.ntp.org, 2.digitallumens.pool.ntp.org and 3.digitallumens.pool.ntp.org via port 123
  4. Router (Gateway) IP Address as configured by DHCP or manually in Commissioner software

DNS

Gateways require DNS via port 53. Gateways default to the following sequence of DNS servers:

  1. DNS server manually configured to gateway using Commissioner software (typically only used in static IP configurations)
  2. DNS server specified by DHCP server
  3. 8.8.8.8 and 8.8.4.4

Proxies

SiteWorx is compatible with transparent proxies that do not alter certificates. An inspecting proxy or other man-in-the-middle that changes certificates will cause the gateways to be unable to authenticate with SiteWorx.

How did we do?