SiteWorx Gateway Connection - IT Information
Firewall Ports
Gateways must be able to connect to reliable high-speed internet, with outbound firewall access to the following standard ports. Inbound access can remain blocked.
- 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 (see more below)
- 6514 (syslog over TLS - TCP): Secure Syslog used for SiteWorx logging and diagnostics
- 53 (DNS - TCP): Domain Name Server, used for DNS lookup (see more below)
NTP
Gateways require NTP in order to authenticate with SiteWorx services. Gateways default to the following sequence of NTP servers:
- NTP server manually configured to gateway using Commissioner software (typically only used in static IP configurations)
- NTP server specified by DHCP server
- 0.digitallumens.pool.ntp.org, 1.digitallumens.pool.ntp.org, 2.digitallumens.pool.ntp.org and 3.digitallumens.pool.ntp.org via port 123
- 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:
- DNS server manually configured to gateway using Commissioner software (typically only used in static IP configurations)
- DNS server specified by DHCP server
- 8.8.8.8 and 8.8.4.4
Firewall Whitelisting
IP Address Whitelisting
SiteWorx does not support whitelisting of IP addresses, as the destination addresses used are dynamic and not static. Instead, whitelist domain names as listed below.
Fully Qualified Domain Names (FQDN)
If whitelisting of destination FQDNs is desired, the following should be listed:
- logs-01.loggly.com:6514
- Additionally, Solarwinds provides a list of static IP addresses for logs-01.loggly.com that can to be whitelisted
- 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.
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, and are thus not compatible.
Related Articles
Gateway Connection Troubleshooting
Live Gateway Connectivity Status Admin users can view the live gateway connectivity status in the Admin Console, which is accessed by clicking the square icon in the top-right and selecting Admin from the dropdown menu. Click Network along the left ...
Advanced Gateway Connection Troubleshooting (HTTP Diagnostics)
This article covers advanced troubleshooting methods to resolve gateway connectivity issues. We recommend these methods be undertaken by Certified Resellers or in partnership with SiteWorx Support. For basic connection troubleshooting, visit Gateway ...
Installer Gateway Connectivity Tool
Resellers have access to an online tool to check gateway connectivity status for newly connected gateways. This is a helpful tool to confirm IT departments have configured ports correctly before traveling onsite for commissioning, or requesting ...
How to Statically Address a Gateway 3 (DLGW3)
This guide only applies to gateways of model DLGW3-LR or DLGW3. These products will have serial numbers beginning in 0202XXXX. Before you Start Gather Necessary Items Micro USB cable Computer, with Commissioner 3.4.1 or later DLGW3 or DLGW3-LR “Live” ...
Convert a DLGW3 from LightRules to SiteWorx
This guide only applies to DLGW3-LR gateways. All DLGW3-LR's have serial numbers beginning in 0202XXXX and have model number "DLGW3-LR" on the front serial number label. DLGW2 units are not compatible. DLGW2 gateways are not compatible with SiteWorx ...