Template Engine SSL Connection Issue

[nagilson]

Build Information

Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=1194329
Build error leg or test failing: Microsoft.DotNet.Cli.New.IntegrationTests.DotnetNewSearchTests.CanDisplayNoResults
Pull request: #51564

Error Message

Fill the error message using step by step known issues guidance.

{
  "ErrorMessage": "The SSL connection could not be established",
  "ErrorPattern": "",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

Similar to #51198

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=1194329
Error message validated: [The SSL connection could not be established]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 11/5/2025 5:19:13 PM UTC

Report

Build	Definition	Step Name	Console log	Pull Request
2964196	dotnet-sdk	Build	Log	#60655
1388539	dotnet/sdk	🟣 Build	Log	#53447
1387575	dotnet/sdk	🟣 Build	Log	#53714
1383021	dotnet/sdk	Build	Log
2953212	dotnet-sdk	Build	Log	#59726
1380895	dotnet/sdk	🟣 Run TestBuild Tests	Log	#53836
1380629	dotnet/sdk	🟣 Run TestBuild Tests	Log	#53557
1378662	dotnet/sdk	Build	Log	#53860

Build	Definition	Test	Pull Request
2962983	dotnet-sdk	Microsoft.DotNet.Cli.Build.Tests.GivenDotnetBuildBuildsCsproj.ItImplicitlyRestoresAProjectWhenBuilding	#60566
1390469	dotnet/sdk	Microsoft.DotNet.Cli.New.IntegrationTests.DotnetNewSearchTests.BasicTest	#54034
1383491	dotnet/sdk	Microsoft.NET.Build.Containers.UnitTests.dll.2.WorkItemExecution	#53941
1380051	dotnet/sdk	Microsoft.NET.Build.Containers.UnitTests.dll.2.WorkItemExecution	#53864
2951443	dotnet-sdk	Microsoft.NET.Build.Containers.UnitTests.dll.2.WorkItemExecution	#59942
1371557	dotnet/sdk	Microsoft.NET.Build.Containers.UnitTests.dll.2.WorkItemExecution	#53745

Summary

24-Hour Hit Count	7-Day Hit Count	1-Month Count
0	2	14

[marcpopMSFT]

If this is still happening, we should ask for help.

[nagilson]

Yes, this is still happening. Speaking with @baronfel, and I think we suspected prior that this is an issue with the runtime in the SSL layer on Mac OS. Do you agree we should raise this with the runtime team?