无法再访问Azure DevOps中的NuGet提要（TF246017 / TF30040）

Question

I recently activated the new URL in Azure DevOps, moving from

https://xxx.visualstudio.com/

to

https://dev.azure.com/xxx

Consequently, the address to my NuGet feed also changed:

https://{xxx.pkgs.visualstudio.com/_packaging/feed.xxx.ca/nuget/v3/index.json

to

https://pkgs.dev.azure.com/xxx/_packaging/feed.xxx.ca/nuget/v3/index.json

Everything works except for one thing. Now, I am unable to access my NuGet feed (using Visual Studio, Visual Studio for Mac & Rider). I end up with the following error:

Attempting to gather dependency information for multiple packages with respect to project 'iOS', targeting 'Xamarin.iOS,Version=v1.0' Unable to load the service index for source https://pkgs.dev.azure.com/xxx/_packaging/feed.xxx.ca/nuget/v3/index.json .

If I type the address in a browser, I get the following error:

{"$id":"1","innerException":null,"message":"TF246017: Azure DevOps Server could not connect to the database. Verify that the instance is specified correctly, that the server that is hosting the database is operational, and that network problems are not blocking communication with the server.","typeName":"Microsoft.TeamFoundation.Framework.Server.DatabaseConnectionException, Microsoft.TeamFoundation.Framework.Server","typeKey":"DatabaseConnectionException","errorCode":0,"eventId":3008}

Question

How do I fix it?

---

Update #1

There is a similar error described in this SO question . I am not using a proxy server.

---

Update #2

I am not seeing this error message when accessing the index.json :

{"$id":"1","innerException":null,"message":"TF30040: The database is not correctly configured. Contact your Azure DevOps Server administrator.","typeName":"Microsoft.TeamFoundation.Framework.Server.AzureClientIPRestrictedException, Microsoft.TeamFoundation.Framework.Server","typeKey":"AzureClientIPRestrictedException","errorCode":0,"eventId":3007}

Answer 1

I posted the same question developercommunity.visualstudio.com and got it fixed. It was due a problem on Microsoft's side as shown on the dev.azure's status page .