Trouble adding NuGet v3 external feeds

I’m having some issues adding NuGet v3 based feeds in Octopus 3.0’s External Feeds list. I’ve tried MyGet and VSTS feeds, but neither succeed to find packages on the /Test screen. I’ve made sure to enter the credentials correctly.

For MyGet, I get the following error:

System.InvalidOperationException: Resource not found for the segment 'v3'. ---> System.Data.Services.Client.DataServiceQueryException: An error occurred while processing this request. ---> System.Data.Services.Client.DataServiceClientException: <?xml version="1.0" encoding="utf-8"?><m:error xmlns:m=""><m:code /><m:message xml:lang="en-US">Resource not found for the segment 'v3'.</m:message></m:error>

For VSTS, I get the following error (sorry, I need to redact some company information below):

System.InvalidOperationException: Could not connect to the feed specified at ''. Please verify that the package source (located in the Package Manager Settings) is valid and ensure your network connectivity. ---> System.Data.Services.Client.DataServiceQueryException: An error occurred while processing this request. ---> System.Data.Services.Client.DataServiceClientException: {"count":1,"value":{"Message":"No HTTP resource was found that matches the request URI '$filter=(substringof('REDACTED.testservice.deployment',tolower(Id)) or ((Title ne null) and substringof('mimeo.facilityprintingservice.deployment',tolower(Title)))) and (IsLatestVersion or IsAbsoluteLatestVersion)&$top=10'."}}

The only way I can fetch packages from MyGet is to use the preauth URL where the token is passed into the URL itself.

Is there some additional step that I need to perform to allow Octopus 3.0 to query against these v3 index.json based feed URLs?



Dalmiro responded to your question via support@ about VSTS, and Damian also responded to your Tweet. Please try not to open 3 different support channels for the same issue. Did you get Damiro’s response? I see that he didn’t directly address the MyGet issue.

As the MyGet team hinted at on Twitter there is no real benefit to using NuGet v3 feed with Octopus. And the current workaround is to use their v2 endpoint instead.

I have added an issue on GitHub for us to decide if and when we will support a v3 feed. Our feeds will be changing soon to allow other styles of artifact types and it will probably be part of that larger overall discussion and decision. You can track the issue here:



Just an update on this. I’ve investigated with the VSTS team and they’ve confirmed it looks like this .NET bug:

There is a link to a hotfix at that URL, but it appears you can only request it by email.

To confirm, are you able to temporarily change your Octopus server machine to a UTC-negative timezone and try again? It’s obviously not a sustainable fix, but it should confirm this is the issue.


HI Damian,

The Octopus server is in New York in the Eastern (EST) timezone, which is already UTC-5 . To answer Vanessa, v2 endpoints work fine and that’s not an issue. The problem is with the v3 endpoints, which is currently required for VSTS. Until VSTS can fix their issues getting their v2 endpoints working, I think we’re stuck.


You’re almost certainly correct. Octopus doesn’t support v3 feeds at the moment, so until VSTS fixes the v2 feed, we’re stuck.

That hotfix didn’t work for me, and after looking closer at the XML that comes back from VSTS, it’s probably not the problem anyway. There are a few dates that come back as 0001-01-01T00:00:00. If you apply any negative timezone offset to that, it’s likely to fail.

I’ve got back in contact with the VSTS team, and I’ll keep you posted.


Hi again,

I’ve received word from the VSTS team that they’ve made some changes that should fix the issue. I tested locally and it seems to work for me.

Can you have another look at adding the v2 endpoint and see if it’s now working for you?


Sorry for not closing on this earlier. But yes, the VSTS nuget v2 endpoints work fine. Thanks!


Thanks for letting us know!