This appears to be an issue with the TFS credentials provider - the 401 status code means credentials were not supplied (and the error message confirms that as well); but typically clients should followup with a 2nd request that includes credentials when the 401 is received. If credentials are actually sent and are invalid/forbidden, then a 403 would be returned by ProGet.

I'm sorry for the difficulty; I can't say I've ever heard of "the server crashes and the only option to recover is to reinstall", but I'm thinking it's something unrelated. All that page does is change a setting in the database that instructs the connector code reads to determine how to configure the proxy. Instead of re-installing, can you investigate the windows event logs and see what errors are happening? Can you give more details about "only option to recover" means? I'm guessing the service crashes, but you can simply start up the service or reboot if that happens.

Hey! It did solve my problem, thank you so much! Have a great week-end. :)

I am one of the developers, which is why I can assure to you that ProGet is not issuing a 503. This is IIS. However, based on the new information you've provided, it's likely happening because of an abrupt Application Pool termination such as a access violation, stackoverflow, etc. In such a situation, it's not possible for ProGet to log anything; the program (AppPool) immediately crashes. Then IIS issues the 503 error. However, IIS should be logging these in the Windows Event log; so if you can look into what it is, then we can try to debug it further. This is an easy scenario for us to set-up, and it's a common error condition, but we cannot reproduce it.

You can configure this via the "BaseUrl" setting in the Admin > Advanced Settings configuration option.

You could install the SQL Tools, but there may be a osql.exe installed that you could have command-line access to.

There are several ways to solve this problem, but a common approach is to multiple servers in each global location, and then either use connectors or replication to ensure the packages are accessible locally.

No problem! Now for a barrage of questions... Where is the 503 response coming from, ProGet or the proxy server? Is there an error message in addition to the status code? What do you mean by "use the ProGet feed", does that mean browsing the ProGet web application (i.e. feed overview page), or accessing packages via nuget.exe/Visual Studio? And does it work as expected if you access ProGet over HTTPS?

A "cached" package is a package that's stored locally so it doesn't have to be downloaded from the external feed, as opposed to a "local package" which is a package that is actually in the local feed. Packages are cached the first time they are requested from the external feed (whether that's by downloading it in the UI, or by using nuget restore, or downloaded via some other tool). Pulling a package downloads a remote package into the local feed as if you pushed it to the feed yourself, so to speak.

This error is related to the UploadReadAheadSize value that is configured in IIS. For IIS7+, see: http://www.iis.net/configreference/system.webserver/serverruntime For IIS6, see: http://msdn.microsoft.com/en-us/library/ms525310(v=vs.90).aspx

We don't, so that means probably in the next week or so; unfortunately this has not been a high-enough priority issue to trigger a maintenance release. Once we have that one, we can do another docker/linux build quite easily.

what a pain in the butt. many of the urls are bound to the page using knockout. These are my rewrite rules I've configured for IIS Rewrite Module with good luck so far. <rewrite> <rules> <rule name="Reverse Proxy to Proget" stopProcessing="true"> <match url="^proget(.*)$" /> <conditions> <add input="{CACHE_URL}" pattern="^(https?)://" /> </conditions> <action type="Rewrite" url="{C:1}://man09120fs:8282/{R:1}" /> <serverVariables> <set name="HTTP_ACCEPT_ENCODING" value="" /> </serverVariables> </rule> <rule name="Reverse Proxy to Proget Resources" stopProcessing="true"> <match url="^Resources(.*)$" /> <conditions> <add input="{CACHE_URL}" pattern="^(https?)://" /> </conditions> <action type="Rewrite" url="{C:1}://man09120fs:8282/Resources{R:1}" /> <serverVariables> <set name="HTTP_ACCEPT_ENCODING" value="" /> </serverVariables> </rule> <rule name="Reverse Proxy to Proget Alerts" stopProcessing="true"> <match url="^alerts$" /> <conditions> <add input="{CACHE_URL}" pattern="^(https?)://" /> </conditions> <action type="Rewrite" url="{C:1}://man09120fs:8282/alerts" /> <serverVariables> <set name="HTTP_ACCEPT_ENCODING" value="" /> </serverVariables> </rule> <rule name="Reverse Proxy to Proget nuget feed" stopProcessing="true"> <match url="^nuget(.+)$" /> <conditions> <add input="{CACHE_URL}" pattern="^(https?)://" /> </conditions> <action type="Rewrite" url="{C:1}://man09120fs:8282/nuget/{R:1}" /> <serverVariables> <set name="HTTP_ACCEPT_ENCODING" value="" /> </serverVariables> </rule> <rule name="Reverse Proxy to Proget feeds" stopProcessing="true"> <match url="^feeds(.+)$" /> <conditions> <add input="{CACHE_URL}" pattern="^(https?)://" /> </conditions> <action type="Rewrite" url="{C:1}://man09120fs:8282/feeds/{R:1}" /> <serverVariables> <set name="HTTP_ACCEPT_ENCODING" value="" /> </serverVariables> </rule> <rule name="Reverse Proxy to Proget package" stopProcessing="true"> <match url="^package/(.+)$" /> <conditions> <add input="{CACHE_URL}" pattern="^(https?)://" /> </conditions> <action type="Rewrite" url="{C:1}://man09120fs:8282/package/{R:1}" /> <serverVariables> <set name="HTTP_ACCEPT_ENCODING" value="" /> </serverVariables> </rule> <rule name="Reverse Proxy to Proget packages" stopProcessing="true"> <match url="^packages/(.+)$" /> <conditions> <add input="{CACHE_URL}" pattern="^(https?)://" /> </conditions> <action type="Rewrite" url="{C:1}://man09120fs:8282/packages/{R:1}" /> <serverVariables> <set name="HTTP_ACCEPT_ENCODING" value="" /> </serverVariables> </rule> <rule name="Reverse Proxy to Proget administration" stopProcessing="true"> <match url="^administration(.+)$" /> <conditions> <add input="{CACHE_URL}" pattern="^(https?)://" /> </conditions> <action type="Rewrite" url="{C:1}://man09120fs:8282/administration/{R:1}" /> <serverVariables> <set name="HTTP_ACCEPT_ENCODING" value="" /> </serverVariables> </rule> <rule name="Reverse Proxy to Proget 0x44" stopProcessing="true"> <match url="^0x44(.+)$" /> <conditions> <add input="{CACHE_URL}" pattern="^(https?)://" /> </conditions> <action type="Rewrite" url="{C:1}://man09120fs:8282/0x44/{R:1}" /> <serverVariables> <set name="HTTP_ACCEPT_ENCODING" value="" /> </serverVariables> </rule> </rules> <outboundRules> <rule name="ProGet outbound rewrite" stopProcessing="true"> <match filterByTags="A, Form, Img, Link, Script" pattern="^/(.*)$" /> <action type="Rewrite" value="http://man09120fs/proget/{R:1}" /> </rule> <!-- 302 Redirects (for the login page, e.g.) need to be rewritten. --> <rule name="ProGet Redirect" preCondition="IsRedirect"> <match serverVariable="RESPONSE_LOCATION" pattern="/(.*)" /> <action type="Rewrite" value="http://man09120fs/proget/{R:1}" /> </rule> <preConditions> <preCondition name="IsHTML"> <add input="{RESPONSE_CONTENT_TYPE}" pattern="^text/html" /> </preCondition> <preCondition name="IsRedirect"> <add input="{RESPONSE_STATUS}" pattern="302" /> </preCondition> </preConditions> </outboundRules> </rewrite>

You need to stop/start the ProGet service (INEDOPROGETSVC) and stop/start the applciation pool (if using IIS).