This is also fixed (BM-3271) starting in v6.1.0

Proget non hub installer on French W2016 Core server with remote SQL db is working fine The pb exist with BuildMaster Hedgehog but not with Otter Best regards Philippe

Assuming you have only ProGet installed, delete the C:\ProgramData\upack directory. This is the location of the directory the Hub installer uses to detect the presence of any of the installed packages. If you have any of the other Hub software installed, you'll have to edit the installedPackages.json file in that directory and remove the entry for ProGet. We'll add a troubleshooting section to the documentation to cover this, and file a bug with the installer itself since this is not supposed to happen.

The connection string used by ProGet is stored in its configuration file (see this documentation page for the format and location). The Windows user account used is whatever user the INEDOPROGETSVC service is running under - generally, ProGet configures this to be NetworkService, but could be configured to be any user account.

There is nothing to re-index. If you see it in the web, then it's already indexed. If the packages appear on the web page, then they will appear in the feed. You can manually inspect the feed with the API if you'd like, or by using a tool like Fiddler or something to see the requests.

Hello Martin, I've filed PG-1422 to stop ProGet from checking whether anonymous users have any feeds they can access. You may also want to check in SSMS whether any of the indexes need to be rebuilt or reorganized.

InedoCore 1.0.10 was accidently released; it was a pre-production version and should not have been shipped. It's since been removed. However, you identified the correct remediation steps: manually restore the old version of the extension. Sorry for the inconvenience.

Thanks, I've filed this as OT-275

In v5, Docker feeds are now under "Containers" in the main navigation.

If you want developers to always be able to use any version of a package, then you should configure a connector to that remote resource. Then, they will always be able to download the latest version of the packages they need, and ProGet will cache those packages.

There is currently no such healthcheck URL; you could use a static resource (like a logo, /resources/images/layout/logo.svg) to see if the web server is responding. That request should be very fast.

UPDATE: this was resolved through our ticket-based support. The underlying issue was "Unable to reach credential server" s3, and it was related to how the credentials were configured in IAM.

Great idea :) See BM-3278

Just to clarify, you can create releases on the "Releases" tab, just "Create New Release". You can have multiple simultaneous releases per application going on, which is ideal for a scenario you describe

Yes! You can use either NuGet or Universal Packages to store your C++ code and packages, and those host those in ProGet.

Keep in mind that retention rules work on an AND basis, so when you select: Delete cached connector packages Delete old versions (all except latest 30 versions) You get only packages that match BOTH of those rules: Only delete cached packages. Never delete the most recent 30 versions of packages. I'm guessing that your packages don't match BOTH those rules;

Ticket is submitted along with additional information

ProGet does not push packages; but you can use a tool like BuildMaster to help build a pipeline for your own nuget packages, and push to different nuget servers along the way.

Could this be related to Quirks mode? https://inedo.com/support/documentation/proget/feeds/nuget#legacy