Setting the following registry setting has resolved this issue:

Key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319 
Value: SchUseStrongCrypto 
Data: 1

I'm afraid this doesn't really help. The server is already configured correctly for TLS, but ProGet doesn't work under this configuration (or at least the external connector to Nuget.org doesn't). I assume ProGet does not require TLS 1.0/1.1 so I need to understand why ProGet is giving this error when run under this configuration

On our UAT PRoGet server we often get sql timeouts performing various tasks. Trying to manage a feed has just resulted in this

[Win32Exception (0x80004005): The wait operation timed out]

[SqlException (0x80131904): Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.]
System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action1 wrapCloseInAction) +3180428 System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) +332 System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady) +4224 System.Data.SqlClient.SqlDataReader.TryConsumeMetaData() +87 System.Data.SqlClient.SqlDataReader.get_MetaData() +99 System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString, Boolean isInternal, Boolean forDescribeParameterEncryption) +584 System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, Boolean inRetry, SqlDataReader ds, Boolean describeParameterEncryptionRequest) +3069 System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource1 completion, Int32 timeout, Task& task, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry) +674
System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) +83
System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method) +301
Inedo.Data.DatabaseContext.ExecuteInternal(String storedProcName, GenericDbParameter[] parameters) +164
Inedo.ProGet.Data.Context.Dashboards_GetDashboardInfo(Nullable1 Packages_Count, Nullable1 IncludeInactive_Indicator) +394
Inedo.ProGet.WebApplication.Pages.Administration.Feeds.Management.ManageFeedPage.CreateChildControls() +926
Inedo.ProGet.WebApplication.Pages.<InitializeAsync>d__2.MoveNext() +197
System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() +31
System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) +60
Inedo.Web.PageFree.<ProcessRequestAsync>d__46.MoveNext() +278
System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() +31
System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) +60
System.Web.TaskAsyncHelper.EndTask(IAsyncResult ar) +64
Inedo.Web.Handlers.AsyncHandlerWrapper.EndProcessRequest(IAsyncResult result) +33
System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +393
System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step) +195
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +128

Our UAT ProGet and database server are both on virtual machines, so I appreciate that performance won't be as good as a physical setup. However I'm wondering if there is a timeout config setting I can change to workaround this error?

Product: ProGet
Version: 5.0.12

Our security team has requested that TLS 1.0 and 1.1 be disabled as they are a security risk. When I do this on our ProGet server I get the following error displayed on my NuGet feed.

There was an error with a connector: The underlying connection was closed: An unexpected error occurred on a receive.

If I re-enable TLS the error goes away.

Product: ProGet
Version: 5.0.12

Ok. So I've created an idential test server which running version 4.6.4. If I push the same package to this server it takes seconds. If I push it to our production server (running 4.7.6) it takes 1 hour. I'm still investigating this to try and pinpoint exactly which version is causing this. But it is looks fairly conclusive to me that something has changed between 4.6.4 and 4.7.6.

Not sure if this is the correct place to raise this but since upgrading from 4.6.4 to 4.7.6 I've seen the time it takes to push a 250Mb Chocolatey jump from 2 minutes to over an hour. I'm going to create a new test server on versiob 4.6.4 to confirm that it is the upgrade which is causing this but that will take some time to setup so wanted to get the ticket logged asap. I'm pretty sure it's related to the upgrade as the problem was seen the day after the server was upgraded and nothing else has changed.

Product: ProGet
Version: 4.7.6

Interesting, thanks for the info. It’s not completely clear to me what the new functionality will involve. You seem to be referring to a server-side “pass-through” connector that connects to the public galleries, but this is not what we’re interested in. We want ProGet to simply host our own extensions in a way that VS recognises. The API that VS uses to talk to a gallery is standard and documented, as it’s just an atom feed ( https://en.wikipedia.org/wiki/Atom_(standard) ). Having an API to upload new extensions would be a bonus, so that we could get TeamCity “publish” jobs to update them, as we do for nuget packages.

I can see Visual Studio Extensions are in your roadmap. I was wondering if you can give any timescales on this? We are having to support these manually in IIS but we use ProGet quite extensively so would be great if we could use this also.

Product: ProGet
Version: 4.6.7