Required Addresses and Ports for Sitrad Pro Communication
Under normal operating conditions, Sitrad Pro does not need to continuously communicate with external servers.
External communication depends exclusively on the features being used (Remote ID, API, P2P, etc.).
However, there is one case that may occur for all users:
✔️ Access to the registration server on first run
In many installations, Sitrad Pro performs an initial machine validation, which may require access to:
https://registration.sitrad.com
After this step, standard operation does not depend on this address, unless Sitrad is reinstalled, the machine is changed, or the registration process is executed again.
After that, other external accesses will depend on the connection mode chosen by the client:
🧩 1. Direct connection to the server (via server IP/DNS)
When it applies:
The client connects directly to the IP address or DNS of the Sitrad server within the same network.
Firewall:
✅ No external allowance is required.
All communication occurs directly between the client machine and the server where Sitrad is installed.
🆔 2. Connection using Remote ID (6-digit code)
When it applies:
The client uses the Remote ID feature (simplified access without needing to know the server IP).
Allow:
https://introducer.sitrad.com
🔗 3. Use of the Sitrad Pro API
When it applies:
Integration with third-party applications or systems via the Sitrad API.
Allow:
https://apimanager.sitrad.com
🌐 4. Use of P2P Tunnel
When it applies:
Remote connections using the encrypted Peer-to-Peer tunnel.
Allow:
https://introducer.sitrad.com
https://apimanager.sitrad.com
https://api.cloud.nabto.com/
*.devices.nabto.net (allow UDP outbound on port 443)
📱 5. Sending push notifications to mobile devices
When it applies:
When the client uses push notifications for Sitrad in mobile applications (Android/iOS).
These notifications use Google Firebase infrastructure.
