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.

Labels:

Popular posts from this blog

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.
Read more

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more