ProGet update checker gives error (error 411)

g.j.spoelstra_9664

The update checker was working in our Proget enviroment for a while today we get this:

INFO: Checking for updates from inedo.com...ERROR: Error checking for updates: System.Net.WebException: The remote server returned an error: (411) Length Required.
at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
at System.Threading.Tasks.TaskFactory1.FromAsyncCoreLogic(IAsyncResult iar, Func2 endFunction, Action1 endAction, Task1 promise, Boolean requiresSynchronization)
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Inedo.ProGet.ScheduledTasks.General.UpdateCheckerScheduledTask.<GetUpdatesXmlAsync>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Inedo.ProGet.ScheduledTasks.General.UpdateCheckerScheduledTask.<ExecuteAsync>d__1.MoveNext()

What could this be?

Product: ProGet
Version: 5.1.4

atripp

It may have been a temporary outage, or a proxy problem, or something. You can ignore it. If you restart the service it will probably go away.

g.j.spoelstra_9664

We still have this issue.. restart of the service does not fix the problem.

First, make sure that the IntegrationUrl property (Advanced Settings) is set to https://inedo.com/pg.

Assuming that it is, then if you're continuing too get the problem, then it means there is a network problem between your ProGet server and Inedo.com. Maybe it's a firewall, proxy server, or something like that.

You may want to check with your network/operations team about this, as they can probably trace/see what's happening between the two

g.j.spoelstra_9664

https://inedo.com/pg/ was set in the advanced settings, ihave changed it to https://inedo.com/pg/update. After a restart from the service, the problem still occurs.
I will ask the network deparpment.

Sorry, I made a mistake.

Please make sure the setting is https://inedo.com/pg/.

If you visit https://inedo.com/pg/update in your browser, you can see the XML that ProGet will otherwise see.

g.j.spoelstra_9664

The strange thing is when i access the url with an internet browser on the machine where proget is installed i get a nice XML.

<?xml version="1.0" encoding="UTF-8"?>
<proget currentVersion="5.1.5"/>

So i think it is a ProGet issue.

ProGet access that URL differently than a web browser, and typically under a different user and proxy context. But I can say that we have thousands of ProGet installations successfully accessing that without receiving 411 errors.

So, this means there is a network problem between your ProGet server and Inedo.com.

Your network folks have tools, like Wireshark, and can diagnose what's happening between.

g.j.spoelstra_9664

Ok i will get back on this after i checked with our network department.

g.j.spoelstra_9664

Dear Alana,

I think your organisation should take problems of your users more seriously, because this issue has been open for two months. You said it was a problem on our side... but now i see in the releasenote from proget 5.1.11 it was a problem on your side.

https://inedo.com/proget/versions#v5.1

It is fixed now.

atripp

We take problems very seriously, but we need to prioritize where to spend engineering resources tracking down problems. This was a edge case that we could not reproduce, and had a very minor impact, and only affected a very small number of free users with a very specific configuration; a free user was able to track down the underlying cause and we fixed it.