"All feeds failed to update" when trying to deploy packages to client

[suzaku9]

While trying to deploy a feeds from the server to a Windows 10 Client, I receive the error "All Feeds failed to Update" on going to the Available Feeds on the client (attached screenshot). The server configuration is set to Insecure Remote Access with a Server HTTP port 9090, with other configurations set to default. The following measures have already been taken to troubleshoot:

1. NI Skyline Service Manager has been restarted and SystemLink Server Configuration shows no issues. Screenshot attached.

2. RabbitMQ had been running into some authentication issues which was fixed with the solution from the following:

https://stackoverflow.com/questions/47893899/authentication-failed-rejected-by-the-remote-node-pleas...

However the error still seems to persist. There is no issue in connecting the client to the server. I can restart the client from the server side if required. Both server and client have internet access. 

[JoshuaP]

You may be hitting a timeout issue that could happen with 18.0 if you have a lot of feeds.  Try upgrading your server to SystemLink 18.1, which improves the amount of time it takes to get the information from the feeds and extends the amount of time it waits for the information to be returned.

SystemLink 18.2 is planned to release in September and it should dramatically improve the amount of time it takes to populate the feeds (~10x improvement).

[suzaku9]

The feeds here are mostly being pulled from the NI Website with just one feed I am trying to deploy from my side (The Test Feed shown in the bottom of one of the attached screenshots). Is there a workaround to remove these NI Feeds being populated and possibly causing the timeout? 

[GreyGrey]

We would recommend updating to 18.1 to get past this issue. The feeds are on the device so that in the case that any of the software installed comes out with a patch or updated, we could remotely upgrade to the new version. If you removed the feeds, you will remove your ability to do that. 

Are you able to make the upgrade to 18.1?

[suzaku9]

I updated the Server and Client to SystemLink 18.1, turned off all the firewalls possible, however the server still seems to time out (see attached screenshot). I also find an error while opening the NI Package Manager on the Client side which is attached. 

[GreyGrey]

Do you use a proxy on your network? Also, can you get the NIPM logs? When used by SystemLink, NIPM is run as the SYSTEM user so you'll have to go to "C:\Windows\System32\config\systemprofile\AppData\Local\National Instruments\NI Package Manager\logs" to find them. I'm interested in any logs (.txt or .log files) in that directory. Don't worry about getting any in any of the subdirectories of that folder. 

[suzaku9]

@GreyGrey There is a company-proxy being used on the network. I'm DMing the logs I have to you. 

[GreyGrey]

I took a look at the logs. It looks like only the SystemLink hosted feeds can't be located by NIPM. Can you try adding an exception to your proxy configuration for the SystemLink server machine on a client that is having trouble finding the packages? Once you've done this, open up NIPM and see if you get any errors about it being unable to access feeds. 

Also, would you mind sharing what proxy server software you use? We are trying to get a better picture of what proxy server software our customers use. Feel free to DM me about this information and whether you can share that.