The Docker Client does not support integrated windows authentication; as a work-around, you'll want to set up a second ProGet site (different port or host name) in IIS that points to the existing folder but doesn't use integrated authentication.

Great to hear it got fixed. Thanks !

You can either use the Release Name for this, or you can use a combination of Build and Release number to create a four part version number ($ReleaseNumber.$BuildNumber)

Please carefully follow the Getting Started with NuGet Feeds in ProGet and Visual Studio tutorial. You need to use the API endpoint URL (shown to you within ProGet's Feed page), not the URL that you at the top of your browser. The /feeds URL is intended for use by a web browser, and the /nuget URL is used for an API (i.e. Visual Studio).

Glad to see it's working; but just as an FYI, the installer does not have any code that can delete the database. That's only in the uninstaller program, and that needs to be manually run with double-confirmation (in the UI).

Just seen that .18 has been release. Tested and working. Ignore above.

Thanks for the report; I've logged this as OT-280

That message is expected, if it's already an updated database. Please check out the restore procedure outlined in Backing Up ProGet instructions

Hello Attila, If you run docker inspect proget -f '{{json .Mounts}}', does it include /var/proget/extensions as both the source and destination of one of the bind mounts?

This is on the all versions page, just click "Traditional Installer".

Thanks Justin; we definitely need to improve docs. I just made a change to it now to clarify this better: https://github.com/Inedo/inedo-docs/blob/master/ProGet/feeds/maven.htm

John, while on the subject of execution ID's and such, during the logging of a psensure, can we add the psensure key to the log so it always outputs what it is checking and validating? How it is now: INFO : 2018-12-11 20:31:07Z - Configuration drift detected. DEBUG: 2018-12-11 20:31:07Z - Adding to execution plan. DEBUG: 2018-12-11 20:31:11Z - Collecting configuration... DEBUG: 2018-12-11 20:31:11Z - Comparing configuration... INFO : 2018-12-11 20:31:11Z - Configuration matches template. DEBUG: 2018-12-11 20:31:14Z - Collecting configuration... DEBUG: 2018-12-11 20:31:14Z - Comparing configuration... INFO : 2018-12-11 20:31:14Z - Configuration matches template. and so on. Maybe it could log something like "Collecting configuration <key>" and "<key> matches template". That way it would make each line meaningful and bring more value into keeping the logs. Eventually I would like to have a way to save a copy of the txt execution into servicenow so we have a record of it in change management system as well. The url you shared previously will help in doing that I think. This improvement would help as documentation for each change. Thanks!

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