Network Requirements: NX Whitelist URLs, Firewall Rules and Ports

🌐 Network Requirements: NX Whitelist URLs, Firewall Rules and Ports

For NX systems to operate reliably, all required cloud services, APIs, and third-party integrations must be reachable from the venue network.
This document outlines all domains, subdomains, and ports that must be whitelisted in your firewall or network security configuration.

⚙️ Overview

NX relies on secure cloud communication between:

• NX POS Devices
• NX Cloud
• Third-party monitoring, analytics, and payment systems

Network restrictions or content filtering can interrupt communication with NX servers, leading to degraded or non-functional POS behavior.
Ensuring proper domain and port whitelisting is essential for real-time operations, payment processing, logging, and analytics.

☁️ NX Cloud API Endpoints

These endpoints provide access to the NX Cloud infrastructure, including venue management, configuration synchronization, reporting, and API services.

✅ Ports Required:

• TCP 443 (HTTPS) — Secure communication for all API calls
• TCP 80 (HTTP) — Used only for fallback or redirection (rarely)

⚠️ Cloud Logging & Monitoring

NX uses Loggly for centralized cloud log collection and analysis.

✅ Ports Required:

• TCP 443 (HTTPS) — Log ingestion via secure API

🔒 Ensure that outgoing logs are permitted over HTTPS. NX does not use UDP syslog forwarding.

📱 Firebase Services (Google)

NX uses Google Firebase for application monitoring, analytics, and messaging.
These endpoints are used by both NX POS and NX Mobile apps.

✅ Ports Required:

• TCP 443 (HTTPS)
• TCP 5228–5230 (for FCM push notifications via Android OS)

💡 If using Android tablets or terminals, ensure that FCM ports (5228–5230) are open for real-time messaging.

🐞 BugSnag (Crash Analytics)

NX uses BugSnag for advanced crash analytics and performance monitoring.

✅ Ports Required:

• TCP 443 (HTTPS) — Secure communication to BugSnag cloud

🔄 MQTT / AWS IoT Messaging

NX POS devices connect to the NX Cloud in real time using MQTT via AWS IoT Core.
This enables live device synchronization, updates, and transaction messaging.

✅ Ports Required:

• TCP 8883 — MQTT over TLS (primary port)
• TCP 443 — MQTT over WebSockets (fallback)

🔒 MQTT uses TLS 1.2+ for all communication. Ensure your firewall allows outbound connections on port 8883.

🧾 NX Payment and Integration Services (when applicable)

Depending on your payment processor and configuration, additional endpoints may be required.
NX POS uses secure HTTPS connections for tokenization, authorization, and settlement.

✅ Ports Required:

• TCP 443 (HTTPS) — Payment and provisioning APIs
• TCP 9000/9100 — Payment and provisioning APIs

🖥️ Additional Cloud Dependencies

NX may communicate with the following common service domains depending on your setup:

⚠️ Time synchronization (NTP) is critical for accurate transaction timestamps and secure token validation.

🔒 Summary: Whitelist Reference

✅ Recommended Firewall Configuration Summary

💬 Key Takeaway

To ensure NX POS and NX Cloud function correctly, allow outbound HTTPS (TCP 443) and MQTT (TCP 8883) traffic to NX, Firebase, Loggly, BugSnag, and AWS IoT domains.
Restrictive firewalls or content filters can prevent app updates, logging, or payment communication, leading to degraded system functionality.