Network configuration for an HDL410 system

URLs to approve for Nureva® Console and troubleshooting tool
Last Updated: October 24th, 2022

Nureva Console and the HDL410 system require a steady connection to the internet.  The URLs below need to be approved if you are using enhanced internet security or use firewalls to allow for a steady connection. The best practice is to connect the HDL410 to an unrestricted outbound network.

NOTE: Nureva Console connections are inbound/outbound initiated. These are bidirectional, non-persistent connections.

  Ensure port 8883 is open and MQTT protocol is allowed on your network.

  Ensure the network uses Dynamic Host Configuration Protocol (DHCP) to assign the IP address.

  Ad blocking can break Nureva's telemetry functionality.

  The HDL410 system does not support proxy server configurations.

URLs to approve



Firmware updates

IoT Hub

System software updates


Ad blocking breaks telemetry functionality (continuous connection)

Troubleshooting connections

The front of the HDL410 connect module features status lights that indicate network and cloud connectivity. If the HDL410 is offline the cloud status LED will turn red and the Nureva Console cloud application will display the device as offline.
  •  Explore the status LEDs for the HDL410 

To help determine the reason for the HDL410 to be offline, Nureva offers a convenient online tool that checks the network configuration and provides a report showing the remedy. Generally, this tool will be used after checking that the LAN is working and one of the following situations applies:

  • A user is unable to enroll an HDL410 to the Nureva Console cloud application 
  • An HDL410 is displaying the Offline status in the Nureva Console cloud application

   Required before you start

  • On the back of the Nureva connect module, locate the network ethernet cable
  • Disconnect this network ethernet cable from the connect module and plug it into the computer that will be used to run this network check

  • Ensure the network settings of the computer used to run the network check mimic how the connect module accesses the network:
    • The computer is using only the same VLAN as the connect module
    • The computer is not using a VPN
    • The computer does not have any proxy configuration enabled

Proceed to the network connectivity tool

Was this article helpful?

Can’t find what you’re looking for?

Contact Support