Skip to main content

The Web Application Project is configured to use IIS. Could not find the server 'https://localhost/SampleApp' on the local machine. Make sure the local IIS server has been configured to support secure communications.

After configuring a new Windows 10 machine, I loaded my first solution to start fixing some bugs. However the web project in my solution failed to load with the following error message:

C:\projects\SampleApp/WebUI.csproj : error  : The Web Application Project SampleApp.WebUI is configured to use IIS.  Could not find the server 'https://localhost/SampleApp' on the local machine. Make sure the local IIS server has been configured to support secure communications.

Whoops! Seems that I forgot to configure something in IIS. I didn’t enable the SSL binding on my local IIS instance.

Let’s fix this!

  • Open up the Internet Information Services(IIS) Manager
  • Click on the Default Website

image

  • Click on Bindings… in the Action pane on the right

image

  • Click on the Add… button to open up the Add Site Binding dialog

image

  • Specify https in the Type dropdown and choose an appropriate SSL certificate from the list

image

  • Click OK to close the dialog. The SSL binding is added to the list

image

  • Click on Close

Now I can reload the web project in Visual Studio without any error…

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