[✨ Triage] dotnet/runtime#117262 by Junjun-zhao - [dotnet-sdk-10.0.100-preview.7.25351.101] EventStore app launch fa ... #1205
Description
Triage for dotnet/runtime#117262.
Repo filter: All networking issues.
MihuBot version: 4431de.
Ping MihaZupan for any issues.
This is a test triage report generated by AI, aimed at helping the triage team quickly identify past issues/PRs that may be related.
Take any conclusions with a large grain of salt.
dotnet/runtime#117262: [dotnet-sdk-10.0.100-preview.7.25351.101] EventStore app launch failed with error "Invalid Configuration: A certificate is required unless insecure mode (--insecure) is set" by Junjun-zhao
[Tool] Searching for Invalid Configuration: A certificate is required unless insecure mode (--insecure) is set, EventStore certificate error .NET 10, dotnet 10 preview certificate required, dotnet 10 preview EventStore regression, dotnet 10 preview.7 certificate (IncludeOpen=True, IncludeClosed=True, IncludeIssues=True, IncludePullRequests=True, Repository=dotnet/runtime)
[Tool] Found 37 issues, 43 comments, 37 returned results (13219 ms)
Here are the most relevant related issues and discussions for triaging issue #117262 ([dotnet-sdk-10.0.100-preview.7.25351.101] EventStore app launch failed with error "Invalid Configuration: A certificate is required unless insecure mode (--insecure) is set"):
1. PR #116732 (June 2025) - Fix dev certificate error on Windows
- Summary: This PR attempts to address a dev certificate error on Windows, referencing issue #116695 (see below). The context is around HTTPS endpoint configuration and developer certificates, which is similar to the certificate error in your report. However, the PR author notes that their change did not resolve the issue in their test log.
- Relevance: Indicates ongoing work and challenges around certificate handling in .NET 10 previews, especially for dev/test scenarios.
2. Issue #116695 (June 2025) - WASM - Dev certificate error on Windows
- Summary: This issue tracks failures to configure HTTPS endpoints due to missing or outdated developer certificates, with the error: "Unable to configure HTTPS endpoint. No server certificate was specified, and the default developer certificate could not be found or is out of date". The error is not identical but is closely related to certificate requirements and regressions in .NET 10 preview builds.
- Relevance: Shows that certificate-related regressions have been observed in .NET 10 preview 7, especially in scenarios where a certificate is required for HTTPS endpoints.
3. Issue #109886 (November 2024) - Error reading exported certificate private key on some machines
- Summary: Users report issues with reading private keys from certificates on Windows 10/11, with errors in .NET 8 and 7. The discussion is about cryptographic exceptions and certificate handling, but not specifically about the "certificate required" error.
- Relevance: Demonstrates ongoing certificate handling issues across .NET versions, but not a direct regression from .NET 10 preview 6 to 7.
4. Issue #55555 (July 2021) - .NET 6 preview 5, The certificate data cannot be read with the provided password, the password may be incorrect.
- Summary: This is about loading certificates in ASP.NET apps and encountering errors when running on Linux, but not Windows. The error is about reading the certificate, not about requiring one.
- Relevance: Related to certificate loading, but not to the regression or the specific error in your report.
5. Issue #31514 (Nov 2019) - The remote certificate is invalid according to the validation procedure
- Summary: This is a long-standing issue about certificate validation failures, especially on Linux, with various workarounds and discussions about OpenSSL and CA trust.
- Relevance: General background on certificate validation, but not a regression or breaking change in .NET 10.
6. Issue #86199 (May 2023) - HttpClient SSL Connection with Client Certificate Fails After Code Change
- Summary: This issue is about client certificate authentication failing after code changes, resolved by cleaning the build. The error is about authentication, not about requiring a certificate.
- Relevance: Related to certificate handling, but not to the regression or the specific error in your report.
7. Issue #21916 (May 2017) - ClientWebSocket client certificate not working with .NET Core
- Summary: This is about client certificate support in early .NET Core versions, with platform-specific issues.
- Relevance: Historical context, not related to .NET 10 or the regression.
8. Issue #81964 (Jan 2023) - Kestrel: Segfault when specifying default certificate on Ubuntu 20.04
- Summary: This is about a crash when specifying a default certificate in Kestrel on Linux, related to OCSP stapling and certificate chain handling.
- Relevance: Shows that certificate handling can break in new .NET versions, but not the same error or regression.
9. Issue #53721 (June 2021) - Unable to find compatible framework version when using preview and not self-contained
- Summary: This is about framework resolution and roll-forward issues with preview SDKs, not about certificates.
- Relevance: Not directly related.
10. PR #116724 (June 2025) - Bump main to .NET 10 Preview 7
- Summary: This PR bumps the main branch to .NET 10 Preview 7. No discussion of certificate issues, but it marks the introduction of the preview version where the regression is observed.
- Relevance: Confirms the timing of the regression.
Key Takeaways
- Regression Confirmed: Your report that the issue is a regression from .NET 10 preview 6 to preview 7 is supported by the timing of related issues and PRs.
- Similar Issues: There are closely related issues and PRs about certificate handling regressions in .NET 10 preview 7, especially around dev certificates and HTTPS endpoints (see #116695 and #116732).
- No Direct Duplicate: There is no direct duplicate of your specific error message with EventStore, but the pattern of certificate-related regressions in preview 7 is clear.
- No Known Workaround: No related issue or PR provides a workaround for this specific regression.
Suggested Next Steps
- Reference issues #116695 and PR #116732 in your issue for context on certificate regressions in .NET 10 preview 7.
- Highlight that this is a regression from preview 6 to 7, as confirmed by your verification matrix and the timing of the preview bump PR.
- Consider tagging the area owners for hosting, security, and compatibility, as this may impact other third-party apps that require certificates.
If you need more details from any of the above issues or PRs, let me know!