Skip to main content

Generate a self-signed certificate for .NET Core

A team member contacted me because he no longer could invoke a local service he was developing. I had a look at the error message the API returned:

One or more errors occurred.
An error occurred while sending the request.
The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.
The remote certificate is invalid according to the validation procedure

This was a local service using a self-signed certificate and it turned out that the certificate was expired.

Time to create a new self-signed certificate…

Create a self-signed certificate using dotnet dev-certs

Generating a new self-signed certificate is easy in .NET Core thanks to the built-in support in the dotnet commandline tool.

Open a command prompt and execute the following command:

dotnet dev-certs https -ep c:\users\BaWu\localhost.pfx -p crypticpassword

Remark:  If the command returns the following response "A valid HTTPS certificate is already present.", a trusted certificate already exists in your store.

Import certificate in IIS

OK, almost there. A last step to get it working in IIS is to import our generated pfx in IIS:

  • Open IIS using inetmgr.
  • Go to Server Certificates.


  • Click on the Import… action on the right. The Import certificate screen is shown.


  • Select the pfx, specify the password and click OK.
  • Now that the certificate is available in IIS, you can change the bindings to use it. Click on the Default Web site(or any other site) on the left.
  • Click on the Bindings… action on the right. The Site Bindings screen is shown.


  • Click on the https item in the list and choose Edit… . The Edit Site Binding screen is shown.


  • Select the newly created SSL certificate from the list and click OK.

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.