Is there an existing issue for this?
Describe the bug
Sometimes after a while the ASP.NET app fails to start when starting from the IDE (Rider) or the console on Linux. The issues starts happening after a few hours, and ususally needs a complete restart of the system to fix.
Details:
Our project is a Aspire project with a single c# backend, postgres db and JS frontend. Both the frontend and the db run without any issue.
When working on the backed and restarting it a lot, sometimes it fails to finish starting up and gets stuck. In this state it prints nothing to the console but it is "running" (has a running process and Aspire tries to connect for the health checks but they obviously fail)
*The aspire console log as viewed from Rider*
At this point I can attach a debugger to see what is happening inside:
*Screenshot of the state the Main Thread is in*
Looking around most of the threads are in a similar state of waiting for something to happen. Except for a worker thread that has:
*Screenshot of the only interesting stack I could find*
If I try the command manually it does run fine and returns data as well showing the cert is in the right place.
Extra info:
Aspire dashboard showing the backedn as unhealthy
Screenshot of the console output after a few things:
- Tried to shut down the backed using the red stop button in Rider that calls the Aspire stop
- After it errored out a bit it gave me the chance to start it again
- This time I set the Log level to Trace to see some info, this is what it gave me.
Expected Behavior
It should start up.
Steps To Reproduce
Sadly no idea here.
Exceptions (if any)
No response
.NET Version
10.0.102
Anything else?
After thinking a bit and reading the code in https://github.com/dotnet/aspnetcore/blob/main/src/Shared/CertificateGeneration/UnixCertificateManager.cs
I decided to try uninstalling certutils. This was provided on my system by: nss-tools-0:3.119.1-1.fc43.x86_64
After uninstalling it the backed maanaged to start up without any issues. This for me suggests that the code was actually hang up on that run of certutil tho I have not idea why.
System and Setup:
- OS: Fedora Atomic (Kinoite) 43
- Dev-env: Everything running inside distrobox
- Dotnet: 10.0.102
- Aspire: 13.1.1
Running dev-certs https --check --trust
gave me: A trusted certificate was found: 19ABAB693E8CC644B4EC95FC396C175DA9D7C669 - CN=localhost - Valid from 2026-02-09 14:46:32Z to 2027-02-09 14:46:32Z - IsHttpsDevelopmentCertificate: true - IsExportable: true
Is there an existing issue for this?
Describe the bug
Sometimes after a while the ASP.NET app fails to start when starting from the IDE (Rider) or the console on Linux. The issues starts happening after a few hours, and ususally needs a complete restart of the system to fix.
Details:
Our project is a Aspire project with a single c# backend, postgres db and JS frontend. Both the frontend and the db run without any issue.
When working on the backed and restarting it a lot, sometimes it fails to finish starting up and gets stuck. In this state it prints nothing to the console but it is "running" (has a running process and Aspire tries to connect for the health checks but they obviously fail)
At this point I can attach a debugger to see what is happening inside:
Looking around most of the threads are in a similar state of waiting for something to happen. Except for a worker thread that has:
If I try the command manually it does run fine and returns data as well showing the cert is in the right place.
Extra info:
Expected Behavior
It should start up.
Steps To Reproduce
Sadly no idea here.
Exceptions (if any)
No response
.NET Version
10.0.102
Anything else?
After thinking a bit and reading the code in https://github.com/dotnet/aspnetcore/blob/main/src/Shared/CertificateGeneration/UnixCertificateManager.cs
I decided to try uninstalling certutils. This was provided on my system by:
nss-tools-0:3.119.1-1.fc43.x86_64After uninstalling it the backed maanaged to start up without any issues. This for me suggests that the code was actually hang up on that run of certutil tho I have not idea why.
System and Setup:
Running
dev-certs https --check --trustgave me:
A trusted certificate was found: 19ABAB693E8CC644B4EC95FC396C175DA9D7C669 - CN=localhost - Valid from 2026-02-09 14:46:32Z to 2027-02-09 14:46:32Z - IsHttpsDevelopmentCertificate: true - IsExportable: true