NPM feed time out error

I have installed ProGet Enterprise trial on Windows 8.1.
If I use the integrated web server everything works fine, but when I use IIS I get a time out error on my npm feed (NuGet and Bower feeds are still working without issues).
I can get rid of the error by removing the connector for https://registry.npmjs.org

This is the error I get when opening the npm feed with the connector configured:

System.Web.HttpUnhandledException (0x80004005): Exception of type 'System.Web.HttpUnhandledException' was thrown. ---> Inedo.Messaging.MessengerException: The operation has timed out. ---> System.TimeoutException: The operation has timed out.
at Inedo.Messaging.ServiceMessenger.SendMessageWithResponse(ServiceMessageBase message)
--- End of inner exception stack trace ---
at Inedo.Messaging.ServiceMessenger.SendMessageWithResponse(ServiceMessageBase message)
at Inedo.ProGet.WebApplication.Pages.NpmFeeds.BrowseNpmFeedPage.GetIndexingStatus(Int32 feedId)
at Inedo.ProGet.WebApplication.Pages.NpmFeeds.BrowseNpmFeedPage.CreateChildControls()
at System.Web.UI.Control.EnsureChildControls()
at System.Web.UI.Control.PreRenderRecursiveInternal()
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.HandleError(Exception e)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest()
at System.Web.UI.Page.ProcessRequest(HttpContext context)
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

Product: ProGet
Version: 3.5.6

Sorry for the delay- I missed this question somehow. I think it's just a problem in the web UI talking to the service. The npm repo itself should still work for clients. Have you tried restarting the ProGet service?

Hi Dean

Restarting the ProGet service solved the problem. Thanks!