500 Server error: Expected an absolute, well formed http URL without a query or fragment


We’ve had to reboot our proget server, since then we’re trying to do a deployment and upon creating a release get an error message:
“500 Server error: Expected an absolute, well formed http URL without a query or fragment.”

Looking at the network tab, the request is this (which does contain a query string):

We’ve tried restarting the octopus service & tentacle, as-well as the proget service as advised in another thread on this board but to no avail.

Any advice appreciated


Hi Daniel, thanks for getting in touch. Can you please let us know the Octopus and Tentacle versions you’re working with, and send the relevant segment from the Raw Task Log (http://docs.octopusdeploy.com/display/OD/Get+the+raw+output+from+a+task)?


Hi Nick,

When you talk about the raw output from the relevant task, it doesn’t look like it creates a task record as it fails before I can do anything on the create release page, but here’s the other details you asked for.


Octopus Deploy:

Exception from chrome network tab:
“errors”: [
“Expected an absolute, well formed http URL without a query or fragment.\r\nParameter name: serviceRoot”,
“System.ArgumentException: Expected an absolute, well formed http URL without a query or fragment.\r\nParameter name: serviceRoot\r\n at System.Data.Services.Client.DataServiceContext…ctor(Uri serviceRoot)\r\n at NuGet.DataServiceContextWrapper…ctor(Uri serviceRoot)\r\n at NuGet.DataServicePackageRepository.GetPackages()\r\n at Octopus.Portal.Areas.Api.Controllers.PackageRepositoryExtensions.d__6.MoveNext()\r\n at System.Collections.Generic.List1..ctor(IEnumerable1 collection)\r\n at System.Linq.Enumerable.ToList[TSource](IEnumerable1 source)\r\n at Octopus.Portal.Areas.Api.Controllers.PackagesController.Versions(String feedId, List1 packageIds)\r\n at lambda_method(Closure , ControllerBase , Object[] )\r\n at System.Web.Mvc.ReflectedActionDescriptor.Execute(ControllerContext controllerContext, IDictionary2 parameters)\r\n at System.Web.Mvc.ControllerActionInvoker.InvokeActionMethod(ControllerContext controllerContext, ActionDescriptor actionDescriptor, IDictionary2 parameters)\r\n at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass37.<>c__DisplayClass39.b__33()\r\n at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass4f.b__49()”

Thanks for the details Daniel, it looks like Octopus is trying to query the NuGet server, but is getting an invalid response.

We’ll need to determine whether the problem is Octopus, or if it’s the NuGet server. The easiest way to isolate this is to add your ProGet server to Visual Studio package manager.

ProGet have some documentation here:

And this page shows how to add the feed source to Visual Studio:

If Visual Studio is successfully able to query the NuGet feed and display packages, then we can look into what Octopus is doing wrong. Hope that helps!