No problem! That worked. Thanks.

If you're running on Windows 2016 or newer, have you tried this?

https://www.intel.com/content/www/us/en/programmable/support/support-resources/knowledge-base/ip/2018/how-do-i-extend-windows-server-2016-file-path-support-from-260-t.html

I tried to join the Inedo Slack channel as described here: https://inedo.com/support/slack but when I try to request an invite to the channel, I see the following message:

*This invite link is no longer active.

If you have an @inedo.com email address, you can still create an account.

If not, please check with the person who shared the invite link with you to ask for an invitation.*

Re: Unable to query https://registry.npmjs.org

We had a ProGet connector to https://registry.npmjs.org working just fine, but then started seeing 401 errors when ProGet was trying to refresh the feed and we were unable to download new package versions.

Following the advice on the thread linked, we created a user at npmjs.org and added it to the connector. It is now working fine.

I have two questions about this:

1. What changed? As far as I understand, you don't need to have an account to download npm packages from npmjs.org (I can do it from the command-line without authenticating). Why does it seem that ProGet needs one?
2. Can someone please confirm that ProGet connectors are unidirectional? ie. you can download packages via a connector, but can't publish via one.

Thanks