Skip to content
English
Contact Support Sign in
Go to kaiterra.com
  • There are no suggestions because the search field is empty.

What Servers and Ports does the Sensedge Go (via Gateway) need to connect to?

If your Sensedge Go Gateway(s) are connecting to a building's Ethernet network, you will need to make sure the following servers and ports are available.

Important: This guide is only applicable if your Sensedge Go Gateway is connecting to a building's Ethernet network. If your gateways are using a cellular connection, these servers and ports do not need to be whitelisted, as the gateway connects via its own cellular network.

Please also note that all of the following connections are outbound only.

The following is a list of essential servers and ports the Sensedge Go Gateway needs to connect to.

Depending on your project, you will have either a Multitech or a RAK gateway. Please refer to the specific section that matches your gateway model to ensure your network is configured correctly.

Multitech Gateways:

Server URL: devicehq.com
Port Type: TCP
Server Port(s): 443, 5798, 5799
Reason: These servers and ports allow for remote troubleshooting and firmware updates for the Gateway. If the connection is blocked, we will be unable to troubleshoot the devices/network, or provide any firmware updates to fix issues/bugs/etc.

Server URL: lora.kaiterra.com
Port Type: TCP
Server Port(s): 443
Reason: This server allows the Gateway to connect to the Kaiterra cloud.
If the connection is blocked, data cannot be uploaded to the Kaiterra Data Platform.

Server URL: time.kaiterra.com
Port Type: UDP
Server Port(s): 123
Reason: This is our NTP server, which is required for gateway operation.
If the connection is blocked, the gateway cannot function.

 --

RAK Gateways:

Server URLs:
  • core-eu.wisdm.network
  • api-eu.wisdm.network
  • ota-eu.wisdm.network
  • log-eu.wisdm.network
Or, use the one below if wildcard rule is supported: *.wisdm.network

Port Type: TCP
Port: 443
Reason: These servers allow for remote troubleshooting and firmware updates for the Gateway.
If the connection is blocked, we will be unable to troubleshoot the devices/network or provide any firmware updates to fix issues/bugs/etc.

Server URL: lora.kaiterra.com
Port Type: TCP
Port: 443
Reason: This server allows the Gateway to connect to the Kaiterra cloud. If the connection is blocked, data cannot be uploaded to the Kaiterra Data Platform.

Server URLs:
  • 0.openwrt.pool.ntp.org
  • 1.openwrt.pool.ntp.org
  • 2.openwrt.pool.ntp.org
  • 3.openwrt.pool.ntp.org
Port Type: UDP
Port: 123
Reason: These are the NTP servers (from the public NTP Pool Project) that the Gateway uses to synchronize its clock. Accurate time is required for TLS handshakes with cloud servers and for the correct timestamping of sensor data. If the connection is blocked, the Gateway cannot function.

Server URLs:
  • 8.8.8.8
  • 1.1.1.1
  • 9.9.9.9
Port Type: ICMP
Port: N/A (ICMP has no port)
Reason: The Gateway periodically pings these well-known public IP addresses to verify that it has a working internet connection. If the connection is blocked, the Gateway will report itself as offline and may attempt to reset its network interface, even if cloud connectivity is otherwise healthy.