One or More Feeds Are Inaccessible Error When Installing Software to NI Linux Real-Time Target

Updated Jan 30, 2026

Reported In

Hardware

  • CompactRIO Controller
  • PXI Controller

Software

  • NI Linux RT System Image

Operating System

  • LabVIEW Real-Time (NI Linux Real-Time)

Issue Details

  • When I try to install software on my NI Linux Real-Time (RT) controller, I receive the message below.  This happens either with the online or offline installation.
    One or more feeds are inaccessible. Check that all feeds are entered correctly and can be reached from the target on this computer.

    OneOrMoreFeedsAreInaccessible_jpg.jpg
 
 

Solution

When installing software on NI Linux RT controllers, the device must access the base image and its feeds. This can be achieved by one of the following methods:

  • The Linux RT target has internet access (online installation)
  • The Linux RT has no internet access, but it can get access to the online repository through a host PC (online installation - via host PC)
  • The Linux RT has no internet access, but it can get access to the offline repository through a host PC (offline installation - via host PC)
  • The Linux RT base image can access the base image and its feeds via a USB Flash Drive.

When the Linux RT can not access the repository, this issue is observed. There could be multiple reasons (firewall, missing software, IP settings, etc) why the Linux RT target can not access the base image and the feeds, but 3 primary reasons have been identified:

  • The Linux RT base image is not installed in the host PC. This can be confirmed via the Installed tab on NI Package Manager (NIPM).

  • Mismatch in the Linux RT base image version installed in the host PC and the Linux RT target. The Linux RT base image installed on the target can be checked in NI MAX by expanding the Software tab, or by right-clicking the Software tab and selecting Add/Remove Software.

  • When the Linux RT tries to access the base repository via the host PC (either offline or online), there might be some network restrictions (i.e. firewall) that block the connection between the host PC and the Linux RT target. In this case,
    • Check the General troubleshooting section in this KB for additional troubleshooting steps.
    • Provide internet access to the Linux RT target (to avoid the use of the host PC) or use the offline method via USB as described in the Installing Software to Offline NI Linux Real-Time Targets KB.

If none of the steps above solve the issue, try the troubleshooting steps described in each of the following sections.
 

Online Installation (no host PC):
If the Real-Time(RT) target has internet access, make sure it can connect to download.ni.com. To check this:

  1. Set up an SSH connection to the RT target from the host PC
  2. Use the following command to ping the NI feed site:  ping download.ni.com.
  3. If the connection is successful, you should get replies as shown below. If not, continue with other troubleshooting below or try the offline installation method below.

  1. Most likely, you won't have any issues using this method, but if you have, check the General Troubleshooting section below.

Offline Installation:

  • To perform an offline installation on the target, follow these steps: Installing Software to Offline NI Linux Real-Time Targets. You’ll need to make sure that both NI Linux Real-Time Offline Installation Support (the version should match the Linux RT base image installed in the Linux RT target) and NI System Configuration are installed in the host computer first. 
  • Verify the connection between the RT controller and the host PC through a ping command to the IP address of your target.
    • Open the Command Prompt in Windows and run the following command: ping <Linux RT IP Address>.
  • Set up an SSH connection in the RT target and make sure you can ping the host PC back: ping <Host PC IP Address>.
  • If you have any issues using this method (via host PC), check the General Troubleshooting section below.

General troubleshooting:

  • If your Real-Time (RT) controller is brand new, ensure that you have installed an NI Linux RT System Image on your host PC using NIPM. 
  • In case you added online feeds manually, check if these feeds are correctly spelled, do not contain any spaces, and that you can access them from a web browser. If the feeds added are not required, try deleting the faulty feeds mentioned in the error message. In NI MAX, right-click the Software tab under the Linux RT target and select Advanced>>Manage Feeds.

  • If this is a PXIe system that you recently migrated from PharLap, make sure its BIOS is updated to the latest version. Download the latest BIOS version from the website and follow the instructions in the downloaded files to proceed with the update. For instance, here is the link for the PXIe-8880 controller: PXIe-8880 Firmware and Additional Drivers Download.

  • When the offline installation process is required, make sure that the connection is not being blocked by the computer’s local firewall or antivirus software. Confirm with your IT team that the port used during the installation process is open. Please check the following article for instructions on how to configure the network firewalls correctly, so they can support NI software: Configuring Software and Hardware Firewalls to Support NI Products.

    • If there is no existing firewall rule to allow communication with the selected port, NI MAX will try to create a new rule called "NI RT Offline Installation". You can check if the rule was properly created on Windows Defender Firewall with Advanced Security » Inbound rules and scroll down until you find said rule (if it exists).

    • If the rule is not present, there might be something in your system (IT policies, third-party software, antivirus, etc.) blocking NI MAX from modifying the firewall rules. In such a case, you can try to create the rule manually to allow NI MAX to open the port and proceed with the installation:
      1. Click on New Rule...

      2. On Rule Type, select Port.

      3. On Protocols and Ports, select TCP and Specific local ports specifying the port NI MAX will use for the installation (i.e. 9100).

      4. On Action, select Allow the connection.

      5. On Profile, check all three boxes.

      6. On Name, you can identify it as desired, but it is suggested to simply name it NI RT Offline Installation.

      7. Restart NI MAX (if it is currently open) to ensure the changes in the firewall are applied.   

Note: If you have problems creating the rule, you might not have the necessary permission to modify your firewall. Please contact to IT team to ensure the rule is created.

 

  • It’s recommended to temporarily turn off the Windows firewall to try to access the download server for the packages being requested. You can use the Troubleshoot Remote System Discovery tool (NI MAX»right-click over Remote Systems) to confirm no firewall or antivirus is blocking the connection. Note: It is important to consider this tool as a quick test and not as a conclusion. Even if the tool does not show any restrictions, you can still be blocked by some company restrictions (firewall, antivirus, network, local settings, etc...).

 

  • Make sure that the NI RT Feed Host Configuration software is allowed to make changes to your computer. If you are not sure if it has the correct permissions, please follow the steps below:
  1. Open Command Prompt as administrator on your PC.
  2. Run the netsh advfirewall reset command, as shown in the image below. This will reset your firewall to its default configuration. 
how-to-reset-windows-firewall-settings-6.png
  1. Go to NI MAX and retry adding software to your RT controller. A window asking for your permission to allow the NI RT Feed Host Configuration software to make changes to your PC may pop up. Click on the Yes button to allow access. Review the following picture for more information. 
allow access.png
 
  • If your computer uses a network proxy, make sure that there is an exception made for download.ni.com. Please follow the steps in the NI Package Manager Fails to Connect Through Proxy Despite Bypass Settings article in order to do so.

  • You can try allowing the RT controller to access the Host PC's internet by enabling the sharing settings for the RT controller's network adapter on the Host PC:

 

Additional Information

In the scenario of a migration from a Phar Lap OS, it's possible that the BIOS originally installed in the target is outdated and might raise some incompatibility issues with the newer NI Linux image versions. In order to avoid this issue, it's important to update the controller's BIOS to the latest available version.