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

DevToys–A swiss army knife for developers

As a developer there are a lot of small tasks you need to do as part of your coding, debugging and testing activities.  DevToys is an offline windows app that tries to help you with these tasks. Instead of using different websites you get a fully offline experience offering help for a large list of tasks. Many tools are available. Here is the current list: Converters JSON <> YAML Timestamp Number Base Cron Parser Encoders / Decoders HTML URL Base64 Text & Image GZip JWT Decoder Formatters JSON SQL XML Generators Hash (MD5, SHA1, SHA256, SHA512) UUID 1 and 4 Lorem Ipsum Checksum Text Escape / Unescape Inspector & Case Converter Regex Tester Text Comparer XML Validator Markdown Preview Graphic Color B

Help! I accidently enabled HSTS–on localhost

I ran into an issue after accidently enabling HSTS for a website on localhost. This was not an issue for the original website that was running in IIS and had a certificate configured. But when I tried to run an Angular app a little bit later on http://localhost:4200 the browser redirected me immediately to https://localhost . Whoops! That was not what I wanted in this case. To fix it, you need to go the network settings of your browser, there are available at: chrome://net-internals/#hsts edge://net-internals/#hsts brave://net-internals/#hsts Enter ‘localhost’ in the domain textbox under the Delete domain security policies section and hit Delete . That should do the trick…

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.