Outstanding, thanks Alex

Looks like this was answered here: https://inedo.com/support/questions/8233 5.0.8 fixes the issue.

The issue is related to packages missing SHA1 hashes in the ProGet databases; at some point packages were able to be added without them. We have updated the migration process internally to perform them if they are missing, and this fix will be included in the next maintenance release. Here is the tracking issue: https://inedo.myjetbrains.com/youtrack/issue/PG-1203

hi Markus, you should be able to put credentials in your Connector. Then you should be able to connect.

This would require writing a custom package store. The disk-based package store does not support this. Perhaps consider using Connectors, or something like that

In order to create a feed-scoped permission, the task must be feed-scopable. Go to Tasks > Customize Tasks, and remove any attributes that aren't marked "F" for feed scopable. Then you can apply to to feeds.

Wonderful! Worked just as you said it would. Thank you very much Alana.

I have created an issue to add a feature to display a better error message when the base url property is invalid.  (PG-1107)

I'm a bit of a loss, because we haven't seen such an error before... and it's not something that ProGet would be doing. You may have some IIS setting enabled, that's intercepting requests and ... doing "something" with them? It's really hard to say, because it simply doesn't make any sense, and the solution will not be found looking in ProGet settings/installation. Would suggest to use the integrated web server in this case. Or, use a fresh IIS installation.

Tagging would indeed be the solution, now it's clear how we should have been working. Thanks for the fast feedback!

That actually worked out very well, thank you for the information. Looking forward to the next release.

Unfortunately there's nothing for us to go on here; with the limited information we have here, everything appears to be fine (the 401 is to be expected when you have an authenticated feed). Because you're using the unsupported VS2013 NuGet Plugin (which we cannot test with), and you upgraded from an a two-year old version of ProGet with a ton of changes between, we have no idea what is going on. We would need to know precisely which requests worked before (request/response), and precisely what it's doing now. Otherwise, you should just consider rolling back to 3.8.6 until you can upgrade to a supported version of Visual Studio.

Ben, That works. Thank you! TLDR; don't use "MultipartFormDataContent" when making this request.

In our testing, we couldn't get the maven feed to crash, but I was able to get an "invalid response" error in Google Chrome when requesting a snapshot from a connector, and I did notice that requesting an old version of a snapshot 404s because ProGet finds the correct version number and then overrides it with the latest version number. We're still investigating...

Hello Robert, Thanks for the bug report! I've filed this as PG-1047. NPM feeds were showing the download count as the total for all NPM packages, not just the ones associated with that feed.

It seems like something changed in security settings - Publish Packages task got "private" scope. I droped "Publishers" and added them again, scope has been changed to "all feeds" and problem gone! Seems it's an upgrade bug because the scope option can't be set in free version...

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

PyPI support has now been added and published as a pre-release version of 5.2.0. Visit the ProGet Versions page to download, or get it from the Inedo Hub download.

ProGet does not currently implement the "_catalog" endpoint currently, which Octopus uses to detect the registry version. It's on our list, but we do not have an ETA for it now.

The url is wrong, and we will update this in the next maintence release