Good news @m-karing_2439 , This works in ProGet 2024! More specifically, when rewriting/refactoring the PyPi feed, we added support for this "unconventional" repository - specifically, one that doesn't follow the /simple convention or use any of the JSON/warehouse api. Cheers, Alana

This is to be expected; unfortunately the Docker Hub does not support searching via API, thus ProGet can't possibly search containers. But you can still get to the container by entering in the name directly in the URL.

Thank you Stijn Peeters, you are spot on! After I performed the migration on our Default feed this morning all packages are showing up as expected when searched for - wahoo! Thanks again!

A 401 means that npm requires authentication which was not supplied, visit Feeds > Connectors > [edit/create npm connector] and enter a username/password to connect to the external registry.

Hi Alana, Thanks so much for the update and the workaround solution. I'll be sure to upvote the linked issue. Best, Michael

Hello all, ProGet 5.1.7 fixes an additional issue that was causing SemVer2 NuGet packages to fail to download: PG-1329

Thanks for the quick update John. Definitely looking forward to the 5.1 release now, once it is out of Beta.

This will be addressed in next maintenance release as PG-1294 . As a workaround, you can access the package directly by version number even without this fix.

I see; my guess is that they have a custom-developed feed, and that feed is only supporting the limited/minimum number of queries required to get it working in the versions of Visual Studio of they support. In other words, it's not a proper feed. ProGet relies on a feed implementing the required API endpoints. In this case, your best bet will be to download the packages from the vendor, and then upload them into your ProGet repository.

Hello Dmytro, I've filed PG-1252 to address this.

The "remote icon" means that there is a package entry in a remote server. If you're continuing to see it, then it may take a little bit for the connector metadata (in memory)cache to be cleared. You could always stop/start the webservice, and then this will go away.

Unfortunately this is a bit tricky to give "general" advice on how to fix, but if you can submit a specific test case that we can reproduce as a ticket, we can research and try to reproduce it,.

This is supposed to check every hour. If it's not, sounds like the service's task runner isn't running. Just restart the service, then its should be ok.

This is the nature of connectors; if npm client asks for "latest" version, then all connectors need to be searched. If you don't want behavior, then you need to remove connectors that have newer versions.

It certainly might... but we haven't evaluated it for performance considerations, etc. Early on, we tried implementing a much more advanced filtering system (author, versions, etc), but it really put a strain on NuGet.org and became useless, so we didn't continue on that featureset. This is the first request for this specific filter, and it might be simple, but we'll definitely consider it.

Hi Alana This page (https://inedo.com/support/documentation/proget/core-concepts/connectors) has no info that I have to link the connector to my feed. Just add a little section at the end with a screenshot so the users sees what he has to do after creating the connector.

This is OS & .NET Framework dependent. Many users have reported that setting the follow registry will resolved this issue: Key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319 Value: SchUseStrongCrypto Data: 1 Note that this will involve a reboot. See this guide on TLS in .NET for more information

Hi, i'm reopening this thread as the public docker connector has been available for a while now, but I can't figure out how to use it. I have the connector set up to point at https://registry.hub.docker.com The setting Do not attempt to search the container registry was automatically enabled. I have a feed public-docker set up to use the connector. The connector shows Active and Healthy, although it shows no known package count (I believe this is expected). Overall, I'm not sure how to use it. The documentation reads as self-conflicting, although I don't know enough about it to say that for sure. That's why I'm asking. From https://docs.inedo.com/docs/proget-docker-connectors: You can also create a connector to an external (non-ProGet) registry such as Docker Hub. This could be useful to whitelist certain base images, or to cache them on your local infrastructure. but then... Many external registries such as Docker Hub do not expose an API for searching and discovery of images, so the ProGet web UI cannot be used to search or browse for images stored in one of these registries via connector. So, i see that I can't search in the UI for images. That's alright, but how can i make sure my docker pull or docker run commands go through the ProGet feed, so the images can be cached, instead of directly out to the Docker Hub? Thanks!

I found this thread after experiencing a similar issue. I was seeing the "string is not a valid semantic version error" from Proget when npm would try to install scoped packages, but only when the npm install was automatically triggered inside Visual Studio by a change to the package.json. We already had the latest version of Proget with the change to the web.config and installs worked fine when running from command line. Problem turned out to be the fact that Visual Studio 2015 had installed it's own copy of the npm.cmd as an external web tool. This was an older version than the one I had installed globally, but the order of external web tool locations in Visual Studio had the path to the older version listed before my system path. Making system path take precedence solved the issue. Just thought I'd post this here in case anyone else with a similar issue stumbles across this thread like I did.

So that would be great if they were indeed added into my packages, but it seems that they are not.