You need to use two hyphens. The flag is `-t` or `--trust`, not `–trust` so the following should work:


```bash
dotnet dev-certs https --trust
```

You can also run the help command to see more info

```bash
dotnet dev-certs https --help
```

[![dev-certs https help output][1]][1]



**See Also**: [How to run `dotnet dev-certs https --trust`?][2]



[1]: https://i.stack.imgur.com/zlr6u.png
[2]: https://stackoverflow.com/q/55485511/1366033

I have a problem with HTTPS when I am running (`dotnet run`) my .NetCore application locally on Windows.
It was working till my localhost certificate expired…

[![][1]][1]

I clean up old certificates and generated the new one by 

    dotnet dev-certs https –clean
    dotnet dev-certs https –trust

I’ve verified that everything was added to certmgr (Personal and Trusted certs), but I have the same problem.
It is keep trying to use old certificate which expired.
I do not know why it is trying to use old “localhost” certificate after clean up certs…

Do you have any idea what should I do?.

Thank you,
Błażej


  [1]: https://i.stack.imgur.com/A6cN6.jpg

How can I use new HTTPS localhost certificate

You can add any ACM certificate you have to a listener, after all this load balancer is a CNAME and would be resolved to your hostname(s) via a DNS record.

However for any ACM certificate you have to be able to verify that you control that domain. As the load balancers domain is owned by Amazon you cannot verify this domain. If you attempt to access the load balancers CNAME directly in the browser it will show as insecure (as the SSL will not be valid for that domain), you will however be able to verify HTTPS works.

The only solution to have a valid HTTPS endpoint will be to use an ACM certificate for a domain you own, and resolve it via that domain name rather than the load balancers CNAME.

I have an Application Load Balancer (ALB) that uses the [default DNS name][1] provided by AWS.  

i.e. name of `my-loadbalancer` in US East is given the DNS name:

`my-loadbalancer-1234567890.us-east-1.elb.amazonaws.com`

[![basic configuration][2]][2]

I have a listener over HTTP that works just fine:

`http://my-loadbalancer-1234567890.us-east-1.elb.amazonaws.com/`

However, when I go to add an **HTTPS Listener**, I need to provide a certificate that matches the current domain.  I can pick something from my ACM store, but they're all for custom domains

[![HTTPS Listener][3]][3]

I can [request a new certificate][4], but not sure how I'd be able to validate against `***.us-east-1.elb.amazonaws.com`

This is a backend service, so I don't need a user friendly domain.

Is there anyway to add HTTPS to a load balancer out of the box?

  [1]: https://docs.aws.amazon.com/elasticloadbalancing/latest/classic/using-domain-names-with-elb.html
  [2]: https://i.stack.imgur.com/b4SOU.png
  [3]: https://i.stack.imgur.com/iSaaP.png
  [4]: https://console.aws.amazon.com/acm/home?region=us-east-1#/wizard/