Aspnetcore.docs: dotnet dev-certs https --trust not working

[jauer13]

When I type in the "dotnet dev-certs https --trust" command, I get... No executable found matching command "dotnet-dev-certs"

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: f2191c25-85c0-80b3-6e0e-f54aaf087150
• Version Independent ID: 5e0ec5a6-a0d1-b78f-b5cc-209f63a66c51
• Content: Get started with ASP.NET Core
• Content Source: aspnetcore/getting-started.md
• Product: asp.net-core
• GitHub Login: @Rick-Anderson
• Microsoft Alias: riande

[guardrex]

Did you install the 2.1 SDK? https://www.microsoft.com/net/download/windows

[EDIT] If you needed to install it, be sure to close and re-open the command window before running the command a second time. It will need to pick up a change to the system PATH after the install.

[Rick-Anderson]

What does dotnet --version show?

[davidgouge]

"No executable found matching command "dotnet-dev-certs"" is the clue.

It looks like you've typed
"dotnet-dev-certs https --trust"
instead of
"dotnet dev-certs https --trust"

Lose the hyphen between dotnet and dev-certs

[Rick-Anderson]

Copy/paste is most reliable.

[BrodaUa]

Getting the same issue. Second command on "Get started with ASP.NET Core" tutorial throws an error....

[Rick-Anderson]

@BrodaUa your Dot net version is too old. Update that.

[cetindogu]

+1

[AlexMcConnell]

On a Mac, not Windows, but...

➜ src git:(master) ✗ dotnet --version
2.1.4
➜ src git:(master) ✗ dotnet dev-certs https --trust
No executable found matching command "dotnet-dev-certs"

Note the version and the lack of hyphen in what I typed.

[sahgilbert]

I'm having a similar problem...

Process

1. Install latest Visual Studio Community 2017 Mac OSX.
2. Install .Net Core 2.1.
3. Install .Net Core 2.2 Preview 3.
4. Create new Asp.Net Core MVC Web App project.
5. Build Solution.
6. Receive prompt to install a trusted HTTPS certificate.
7. Click yes to install certificate.
8. Receive System.InvalidOperationException in Program.cs.

Exception

"Unable to configure HTTPS endpoint. No server certificate was specified, and the default developer certificate could not be found.\rnTo generate a developer certificate run 'dotnet dev-certs https'. To trust the certificate (Windows and macOS only) run 'dotnet dev-certs https --trust'.\rnFor more information on configuring HTTPS see https://go.microsoft.com/fwlink/?linkid=848054."

Screenshot

Follow Up

I ran the commands from the "Get Started with Asp.Net Core" link in the first comment on this issue and got the following -

[Rick-Anderson]

@sahgilbert

Install .Net Core 2.2 Preview 3.
Uninstall that. It uses the latest SDK.

[Rick-Anderson]

@sahgilbert
Follow the instructions

o generate a developer certificate run 'dotnet dev-certs https'. To trust the certificate (Windows and macOS only) run 'dotnet dev-certs https --trust'.

[sahgilbert]

Thanks, it turned out to be an issue with my keychain. I’ve nuked that and
started again, which succeeded.

On Tue, 13 Nov 2018 at 18:22, Rick Anderson [e-mail]
wrote:

@sahgilbert https://github.com/sahgilbert
Follow the instructions

o generate a developer certificate run 'dotnet dev-certs https'. To trust
the certificate (Windows and macOS only) run 'dotnet dev-certs https
--trust'.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/aspnet/Docs/issues/6820#issuecomment-438381782, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AM1FybfMiM3XpsGTI8yi5vSlPD-QaiWBks5uuw3mgaJpZM4UX1VX
.

[zqw1998]

Thanks, it turned out to be an issue with my keychain. I’ve nuked that and started again, which succeeded.
…
On Tue, 13 Nov 2018 at 18:22, Rick Anderson @.*> wrote: @sahgilbert https://github.com/sahgilbert Follow the instructions o generate a developer certificate run 'dotnet dev-certs https'. To trust the certificate (Windows and macOS only) run 'dotnet dev-certs https --trust'. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#6820 (comment)>, or mute the thread https://github.com/notifications/unsubscribe-auth/AM1FybfMiM3XpsGTI8yi5vSlPD-QaiWBks5uuw3mgaJpZM4UX1VX .

Hi could you share how did you deal with the keychain because I'm having the same problems.

[Evert-Arends]

I'm having trouble myself too, if anyone has found another way to fix this it would be greatly appreciated!
Version:

dotnet --version
2.1.403

[Rick-Anderson]

@Evert-Arends what OS? What was the error? Can you try repairing/reinstalling the SDK?

[refex]

I have the same problem.

tried to launch

dotnet dev-certs https --trust
Cannot find command 'dotnet dev-certs', please run the following command to install

dotnet tool install --global dotnet-dev-certs

then

dotnet tool install --global dotnet-dev-certs
Tool 'dotnet-dev-certs' is already installed.

my environment

dotnet --info
.NET Core SDK (reflecting any global.json):
 Version:   2.1.402
 Commit:    5b8776a9a4

Runtime Environment:
 OS Name:     arch
 OS Version:  
 OS Platform: Linux
 RID:         arch-x64
 Base Path:   /opt/dotnet/sdk/2.1.402/

Host (useful for support):
  Version: 2.1.4
  Commit:  85255dde3e

.NET Core SDKs installed:
  2.1.402 [/opt/dotnet/sdk]

.NET Core runtimes installed:
  Microsoft.NETCore.App 2.1.4 [/opt/dotnet/shared/Microsoft.NETCore.App]

To install additional .NET Core runtimes or SDKs:
  https://aka.ms/dotnet-download

[guardrex]

Did u see the other convo regarding Arch? For one thing, it isn't a supported platform. However, they may have had some progress via community updates and/or a workaround. See :point_right: https://github.com/aspnet/Docs/issues/9195

[Rick-Anderson]

@refex see https://docs.microsoft.com/en-us/aspnet/core/security/enforcing-ssl?view=aspnetcore-2.1&tabs=visual-studio#trust-the-aspnet-core-https-development-certificate-on-windows-and-macos

To trust the certificate run 'dotnet dev-certs https --trust' (Windows and macOS only).
For establishing trust on other platforms refer to the platform specific documentation.

[Evert-Arends]

I am on Manjaro linux

dotnet --info
.NET Core SDK (reflecting any global.json):
Version: 2.1.403
Commit: 04e15494b6

Runtime Environment:
OS Name: manjaro
OS Version:
OS Platform: Linux
RID: arch-x64
Base Path: /opt/dotnet/sdk/2.1.403/

Host (useful for support):
Version: 2.1.5
Commit: 290303f510

.NET Core SDKs installed:
2.1.403 [/opt/dotnet/sdk]

.NET Core runtimes installed:
Microsoft.NETCore.App 2.1.5 [/opt/dotnet/shared/Microsoft.NETCore.App]

To install additional .NET Core runtimes or SDKs:
https://aka.ms/dotnet-download

Quick fix for Arch based distro's:
I found out that SSL is not (yet?) specifically supported for (arch based) linux, so if anyone just wants to work and not be bothered by this, remove the "https://localhost:5001;" from your applicationUrl in launchSettings.json. This is environment specific and should not be pushed, so any other developers working on your project will not bothered by it.

[jwh315]

Thanks, it turned out to be an issue with my keychain. I’ve nuked that and started again, which succeeded.
…
On Tue, 13 Nov 2018 at 18:22, Rick Anderson @.*> wrote: @sahgilbert https://github.com/sahgilbert Follow the instructions o generate a developer certificate run 'dotnet dev-certs https'. To trust the certificate (Windows and macOS only) run 'dotnet dev-certs https --trust'. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#6820 (comment)>, or mute the thread https://github.com/notifications/unsubscribe-auth/AM1FybfMiM3XpsGTI8yi5vSlPD-QaiWBks5uuw3mgaJpZM4UX1VX .

Hi could you share how did you deal with the keychain because I'm having the same problems.

for mac os users facing this issue. I did the following.

1. Open Keychain
2. Click on Certificates
3. find the cert for localhost, right click and delete
4. terminal enter dotnet dev-certs https

[w0244079]

Is creating a dev cert supported in Centos7 with dotnet version 2.2.104?
I attempted running dotnet dev-certs https --trust (as the instructions say to do)
The --trust flag was not recognized.
I was able to create a cert by simply removing the --trust flag...however the browser complains as it is not trusted? What's the scoop on this?

[christianwico]

I don't know. It seems that the --trust flag is no longer there? Having the same issue, too.

$ dotnet dev-certs https --trust
Specify --help for a list of available options and commands.

$ dotnet dev-certs https --help
Usage: dotnet dev-certs https [options]

Options:
  -ep|--export-path  Full path to the exported certificate
  -p|--password      Password to use when exporting the certificate with the private key into a pfx file
  -c|--check         Check for the existence of the certificate but do not perform any action
  --clean            Cleans all HTTPS development certificates from the machine.
  -v|--verbose       Display more debug information.
  -q|--quiet         Display warnings and errors only.
  -h|--help          Show help information

$ dotnet --version
2.2.105

[guardrex]

@HakuFlou That option is for Windows and macOS only. See the note .....

ASP.NET Core

Successfully installed the ASP.NET Core HTTPS Development Certificate.
To trust the certificate run 'dotnet dev-certs https --trust' (Windows and macOS only).
For establishing trust on other platforms refer to the platform specific documentation.
For more information on configuring HTTPS see https://go.microsoft.com/fwlink/?linkid=848054.

You should consult the docs of the platform's provider.

[esbgo97]

Hi, sorry for my English, I found this solution that works for me:

1. uninstall dotnet-dev-certs
   $: dotnet tool uninstall --global dotnet-dev-certs
   2.reinstall
   $: dotnet tool install --global dotnet-dev-certs
2. add path, replace [user] for your user:
   $: export PATH="$PATH:/home/[user]/.dotnet/tools"
3. execute again:
   $: dotnet dev-certs https --trust

if want to keep this after reboot need add path on ~/.bash_profile

[Rick-Anderson]

@esbgo97 See #13928