Troubleshooting System Connection Issues

Troubleshoot systems with connection issues.

  1. In the SystemLink web application, click System Management » Systems.
  2. Hover over the connection status icon for your system to see the status message.
  3. Use the following table to understand and troubleshoot the connection status of your system.
    Icon Status Message Description


    		The system is connected. The system is fully connected via SaltTCP (4505, 4506) and has successfully authenticated with the SystemLink server via the /niauth/v1/auth HTTP route.


    		The system is disconnected. The system is is not connected via SaltTCP (4505, 4506). See the SaltStack communication model documentation for more information.


    		The system is approved but it did not try to connect yet. The system has been approved by an authorized user, but it is not trying to connect to the SystemLink server.


    		The system is connected and the refresh job is running. The system is fully connected via SaltTCP (4505, 4506) and is currently running the initial refresh job to complete the connection.


    		The system is connected but the refresh job failed. The system has attempted to execute 5 refresh jobs and each one has failed. Ensure that the SystemLink client and its dependencies are properly installed and running.


    		The system is activated but the connection is not established yet. The system has been activated but needs to be approved by an authorized user.


    		The system is connected but it cannot publish data.
    The system can communicate with the server over SaltTCP (4505, 4506), but cannot reach or authenticate the server over HTTP. Complete the following steps to troubleshoot.
    1. Check that you are specifying the fully qualified domain name of the SystemLink server in the SystemLink client tray app on Windows or NI MAX on NI Linux RT.
    2. Ensure that your security certificate has not expired and that the system can reach the appropriate certificate authority.
    3. Regenerate the system API key by changing the workspace of the system or deleting it from the server and reconfiguring the client to connect again.
    Note Deleting the system removes all tracked data about the system from the server.