Skip to main content

Azure DevOps Server - Switch from HTTP to HTTPS–Part 4

With the release of Azure DevOps Server 2022, I thought it would be a good time to finally make the switch to HTTPS for our internal Azure DevOps server. With the idea to minimize downtime, I decided to first introduce the HTTPS endpoint before upgrading the Azure DevOps server. But o boy, what I thought would be an easy task turned out to be quite a journey.

In part 1 I explained the steps that should be done at the server side, in part 2 I continued with an explanation of the changes done on the client side. In the third and what I thought would be the final part I had a look at the errors I got on the build server.

But here I'm back again with a fourth part, and yes I promise this will be the last one.

Although I thought I had fixed everything, I got another error when I tried to build an application(both in Visual Studio and through the Azure DevOps build pipeline). I first noticed the problem when building through Azure Pipelines, here is the error I got:

It seems that NuGet couldn’t find and restore the NuGet packages.

When I had a look at the beginning of the NuGet task it became quite obvious why:

The pipeline was still using the old http based Azure Artifact endpoint instead of the new https endpoint.

Ok, let’s see how we can fix this…

Updating the NuGet Package Source

If you got this error in your build pipeline, it probably means that you have configured your NuGet restore task with the ‘Feeds in my Nuget.config’ option:

As you know there are multiple ways you can specify the source of your NuGet packages and one of them is through a nuget.config file. Visual Studio will also use this file if it is found in your solution or project directory.

So to get rid of the error and be able to successfully restore our NuGet packages, we need to update our Nuget.config file to use our HTTPS endpoint:

Remark: Be aware that there is also a global Nuget.config file, it can be possible that you have your Package Source configured there. You can find this global Nuget.config file in the following location:


If you need to update the list of Package Sources in Visual Studio, go to the Visual Studio Options --> NuGet Package Manager --> Package Sources and update the URL there:


Popular posts from this blog

XUnit - Assert.Collection

A colleague asked me to take a look at the following code inside a test project: My first guess would be that this code checks that the specified condition(the contains) is true for every element in the list.  This turns out not to be the case. The Assert.Collection expects a list of element inspectors, one for every item in the list. The first inspector is used to check the first item, the second inspector the second item and so on. The number of inspectors should match the number of elements in the list. An example: The behavior I expected could be achieved using the Assert.All method:

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

Angular --deploy-url and --base-href

As long you are running your Angular application at a root URL (e.g. ) you don’t need to worry that much about either the ‘--deploy-url’ and ‘--base-href’ parameters. But once you want to serve your Angular application from a server sub folder(e.g. ) these parameters become important. --base-href If you deploy your Angular app to a subfolder, the ‘--base-href’ is important to generate the correct routes. This parameter will update the <base href> tag inside the index.html. For example, if the index.html is on the server at /angularapp/index.html , the base href should be set to <base href="/angularapp/"> . More information: --deploy-url A second parameter that is important is ‘--deploy-url’. This parameter will update the generated url’s for our assets(scripts, css) inside the index.html. To make your assets available at /angularapp/, the deploy url should