Skip to main content

Azure DevOps Server–Switch from HTTP to HTTPS–Part 1

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.

Updating IIS

Let’s start with the simple stuff and update our IIS instance to introduce a second binding:

  • Log in on your Azure DevOps server instance.
  • Open the Internet Information Services (IIS) Manager.

  • Select the Azure DevOps Server site on the left and click on Bindings… on the right.

  • On the Site Bindings window choose Add…

  • On the Add Site Binding window, select HTTPS from the Type dropdown and select the correct SSL certificate. Optionally you can also set a hostname.

  • Click OK and Close.

Now you can already test if the new binding is working by browsing to the HTTPS endpoint you’ve just created.

Updating Azure DevOps Server

Although doing the changes in IIS is already sufficient to be able to start using the HTTPS endpoint, when Azure DevOps itself communicates about its URL it will be still using the old HTTP based endpoint.

To change this, we have to update the Public URL:

  • Open the Azure DevOps Server Administration Console.

  • Click on Change Public URL.
  • Specify our HTTPS endpoint and click on Test. If the test succeeds succesfully, click on OK to apply the change.

More information: Setting up HTTPS - Azure DevOps | Microsoft Learn

So far, so good. But these are only the changes that need to be done on the server. Tomorrow, we’ll have a look at what needs to be done on the client.

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.