This page is for the people who run the network and the firewall at a site that uses Hermetry. It lists every connection Hermetry needs, which side opens it, the port, and where the app shows the exact host name.
The rules in short
- Every connection from your site is outgoing. Browsers, devices, LoRaWAN gateways and licensed routers connect out to Hermetry. Nothing on your site needs to accept connections from the internet. The one exception is a device that Hermetry polls; see the section on devices Hermetry connects to below.
- Write rules on host names, not IP addresses. Hermetry does not publish fixed IP addresses for these hosts. Devices must connect by host name in any case, because the TLS check of the server certificate needs the name.
- Use the hosts of your organisation’s region. Each region is a separate deployment with its own host names. A device or gateway connects to the hosts of the region your organisation lives in. See Regions and data residency.
Where to find each host name
You do not need to guess a host name. The app shows each one where you need it.
| Host | What it is | Where the app shows it |
|---|---|---|
| Your organisation’s address | The free address <slug>.<platform domain>, and any custom domain you added | Domains in the Organisation part of the menu. See Web addresses and custom domains |
| Broker host | The MQTT host your devices connect to | The Connection details card on the device page |
| HTTPS device address | The base address of the device HTTP API | The Connection details card on the device page |
| Network server address | The secure websocket address your LoRaWAN gateways connect to, wss://<slug>.<network server host> | The gateway’s LoRaWAN tab. See Your network server address |
| Firmware download address | A short-lived HTTPS link in the device’s fw_url attribute | Sent to the device with each update. See Firmware updates (OTA) |
The device connection details are also available through the API: GET /api/iot/devices/{deviceId}/connection. The answer holds the broker host, port and TLS flag and the HTTPS base address, and nothing secret. See Devices and profiles API.
Ports to allow from your site
| Connection | From | To | Protocol and port |
|---|---|---|---|
| Web app and REST API | Browsers, scripts and integrations | Your organisation’s address and the platform’s own sign-in address | HTTPS on TCP 443 |
| Live updates in the app | Browsers | The same address as the app | Websocket over HTTPS on TCP 443 |
| MQTT devices | Devices and gateways | The broker host | MQTT 3.1.1 over TLS on TCP 8883 |
| MQTT devices without TLS | Devices of a profile that allows plain MQTT | The broker host | MQTT on TCP 1883, only where the installation runs the plain listener |
| HTTPS devices | Devices | The HTTPS device address, paths under /api/v1/ | HTTPS on TCP 443 |
| LoRaWAN gateways | Basics Station gateways and licensed routers with a LoRa radio | The network server address | Secure websocket (wss://): TCP 443 when the address shows no port, otherwise the port in the address |
| Firmware downloads | Devices | The host in fw_url, then the file storage host it may redirect to | HTTPS |
| Remote access to a router’s panel | Licensed routers | The platform’s tunnel address, which the router receives when a session opens | TLS (secure websocket) |
| Remote access to a router’s panel | Your members’ browsers | The panel address, on a separate domain from Hermetry | HTTPS |
Plain HTTP on TCP 80 redirects the app to HTTPS. Devices use port 80 only when they cannot do TLS and the installation offers plain HTTP for the device API.
Important
Device profiles are TLS only (port 8883) by default. A device that logs in on port 1883 is refused unless its profile allows plain MQTT. Keep port 1883 closed unless you have such a profile. See Device transport security.
Notes on each connection
- Broker host. The card may show your organisation’s own address or the region’s broker host. Copy it exactly as shown, and let the device verify the server certificate against the host name. See MQTT.
- HTTPS device address. The device API answers on
/api/v1/of the address on the card. See Device HTTP API. - Network server address. All gateways of your organisation use the same address. It follows your organisation’s web address name, so it changes when an administrator changes that name.
- Firmware downloads. The
fw_urllink is valid for 15 minutes by default, and the device resumes a broken download with an HTTPRangerequest. The link may answer with a redirect to the file storage host of your region, so a device must follow redirects, and your firewall must let it reach that host too. - Remote access. The router dials out when you select Open panel; it needs no fixed IP address and no open port. The panel opens in a new tab on its own address, on a different domain from Hermetry. See Remote access to a router’s panel.
- File uploads in the browser. When your region stores files in an object store, the browser can upload a file straight to that store. If your network allows only listed host names, allow the file storage host as well.
Devices Hermetry connects to
Some devices cannot connect out: an SNMP agent in a UPS, a camera, a recorder. For these, Hermetry’s poller connects to the device. This is the only case where your site accepts a connection from the internet.
| What | Direction | What to allow |
|---|---|---|
| SNMP agents and other polled boxes | Hermetry to your device’s public address | The device’s own port, from the platform’s addresses only |
| Cameras and recorders | Hermetry to your camera’s public address | The camera’s HTTP and RTSP ports, from the platform’s addresses only |
When the installation names the fixed addresses the poller connects from, the endpoint form shows them: “The platform connects to the device from …. Allow these addresses in the firewall of the site.” Allow only these addresses, and only to the device’s port.
Private, loopback and link-local addresses are refused. To reach devices on a private network without a public address or port forwarding, put a Hermetry Edge on the site network. See Protocol endpoints and Add a camera or recorder.
Connections from Hermetry to your services
Webhooks, the HTTP request and MQTT out blocks of flows, and polled endpoints connect out from Hermetry to addresses you enter. Your receiving server must accept these connections on the port in its URL. Hermetry refuses private, loopback and internal addresses for them after resolving the name. See Webhooks and Connections and secrets.
Check a connection from your site
Run these from a computer on the same network as your devices. Replace the host with the one the app shows.
# The broker: the handshake must end with "Verify return code: 0 (ok)"
openssl s_client -connect <broker host>:8883 -servername <broker host> </dev/null
# The web app and the device HTTP API
curl -sI https://<your organisation's address>/
# The network server (no port in the address means 443)
openssl s_client -connect <network server host>:443 -servername <network server host> </dev/null
A timeout means a firewall drops the connection. A certificate error usually means the device connects by IP address, has no CA bundle, or its clock is wrong. See A device does not connect.

