Skip to main content

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

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.

Yesterday I explained the actions required on the server side, today we move on to the client side.

Visual Studio TFVC workspaces

In Visual Studio, we have to update our connections in Team Explorer.

  • Therefore click on the green Connect icon in Team Explorer.

  • Click on Manage Connections and Connect to a project…

  • Right click on the existing connection and choose Remove from the context menu.

  • Click on Add TFS server, enter the updated Server URL and click on Add.

  • Restart your Visual Studio instance.

After doing these steps, I noticed that still the original URL was shown when I reopened a project in Visual Studio:

There is one last step you need to take for your TFVC workspaces:

Remark: You need to repeat this command for every Visual Studio version you have installed on your dev machine.

GIT repositories

For our Git repositories, we need to update our remote origin. We can do this through the command line:

git remote set-url origin <remote-url>

You can verify that the remote’s URL was successfully changed by listing the remote connections:

git remote -v

You can also update the remote origin through Visual Studio:

  • From the Git menu, choose Manage Remotes.

  • Select the remote origin and click on Edit.

  • Update both URL’s and click on Save.

Important:

By default, projects that use Git for version control will fail to validate the SSL certificate you have configured for Azure DevOps Server.

This is because unlike Azure DevOps Server and Visual Studio, Git does not recognize the Windows certificate store. Instead, it uses OpenSSL for its certificate store. A solution is to register your certificate in OpenSSL, luckily an easier solution is available since Git for Windows 2.14. You can configure Git to use SChannel, the built-in Windows networking layer. This means that it will use the Windows certificate storage mechanism and you do not need to explicitly configure the curl CA storage mechanism.

Therefore execute the following command:

git config --global http.sslbackend schannel

More information:

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