Aspnetcore: An error occurred attempting to determine the process id of dotnet.exe

Created on 22 Aug 2016  路  9Comments  路  Source: dotnet/aspnetcore

When attempting to run my application with SSL enabled, I get the following error:

An error occurred attempting to determine the process id of dotnet.exe which is hosting your application. One or more errors occured.

It seems to happen when the App URL begins with 'https://' regardless of whether Enable SSL has been selected. What would be causing this error?

Most helpful comment

I came here searching for help on this same issue. The fix for me was found in Vackups answer to this Stack Overflow question

In short, the fix for me was this:
"So, running the site with Ctl+F5 installed the certificate and then I was able to debug the site solving my issue."

All 9 comments

How did you configure it?

What do you mean?

Can you put your application(GitHub preferable) somewhere where we can reproduce the problem.

I came here searching for help on this same issue. The fix for me was found in Vackups answer to this Stack Overflow question

In short, the fix for me was this:
"So, running the site with Ctl+F5 installed the certificate and then I was able to debug the site solving my issue."

That did it - thank you!

Thank you. I was going crazy why this error comes up after enabling ssl. 馃憤

I did this: (StackOverflow: An error occurred while attempting to determine the process id of dotnet.exe which is hosting your application. One or more errors occurred)

I had been messing with some certificates, so I had removed the IIS Express certificate. So easiest way to reinstall the certificate I found before coming here was to go into add/remove programs and run fix IIS Express, which installs the certificate again. Not sure if Ctrl+f5 does the same thing.

After that I had to disable and re-enable ssl.

This does not really feel like a developer solution, more trying and failing, but it worked!

Closing this issue because it isn't clear to me if there is an issue remaining. If you feel there's still an issue, please re-open this issue or log a new issue with complete details of the problem. Thanks!

Was this page helpful?
0 / 5 - 0 ratings