Failed to acquire .Net runtime, download times out

[edfrutos]

Does this occur consistently?
Repro steps:

Action: azextAgent.activate
Error type: Error
Error Message: Failed to acquire .NET runtime

Version: 0.3.61
OS: darwin
OS Release: 24.2.0
Product: Visual Studio Code
Product Version: 1.96.2
Language: es

Call Stack

extension.bundle.js:2:1804577
fulfilled extension.bundle.js:2:1803733

[JasonYeMSFT]

@edfrutos This is a duplicate of #56. Could you please reproduce it and share the logs as suggested in the linked issue?

[edfrutos]

An error occurred while installing .NET: .NET Acquisition Failed: .NET install timed out.
You should change the timeout if you have a slow connection. See: https://github.com/dotnet/vscode-dotnet-runtime/blob/main/Documentation/troubleshooting-runtime.md#install-script-timeouts.
Our CDN may be blocked in China or experience significant slowdown, in which case you should install .NET manually., MESSAGE: Command failed: "/Users/edefrutos/.vscode/extensions/ms-dotnettools.vscode-dotnet-runtime-2.2.3/dist/install scripts/dotnet-install.sh" -InstallDir "/Users/edefrutos/Library/Application Support/Code/User/globalStorage/ms-dotnettools.vscode-dotnet-runtime/.dotnet/8.0.11~x64~aspnetcore" -Version 8.0.11 -Verbose -Runtime aspnetcore -Architecture x64
dotnet_install: Error: Could not find ASP.NET Core Runtime with version = 8.0.11
dotnet_install: Error: Refer to: https://aka.ms/dotnet-os-lifecycle for information on .NET Core support
, CODE: 1, SIGNAL: null, Error: .NET install timed out.
You should change the timeout if you have a slow connection. See: https://github.com/dotnet/vscode-dotnet-runtime/blob/main/Documentation/troubleshooting-runtime.md#install-script-timeouts.
Our CDN may be blocked in China or experience significant slowdown, in which case you should install .NET manually., MESSAGE: Command failed: "/Users/edefrutos/.vscode/extensions/ms-dotnettools.vscode-dotnet-runtime-2.2.3/dist/install scripts/dotnet-install.sh" -InstallDir "/Users/edefrutos/Library/Application Support/Code/User/globalStorage/ms-dotnettools.vscode-dotnet-runtime/.dotnet/8.0.11~x64~aspnetcore" -Version 8.0.11 -Verbose -Runtime aspnetcore -Architecture x64
dotnet_install: Error: Could not find ASP.NET Core Runtime with version = 8.0.11
dotnet_install: Error: Refer to: https://aka.ms/dotnet-os-lifecycle for information on .NET Core support
, CODE: 1, SIGNAL: null
at f.next (/Users/edefrutos/.vscode/extensions/vscode-dotnet-runtime-library/dist/Acquisition/AcquisitionInvoker.js:69:50)
at Generator.next ()
at s (/Users/edefrutos/.vscode/extensions/vscode-dotnet-runtime-library/dist/Acquisition/AcquisitionInvoker.js:5:58)

[JasonYeMSFT]

The error message suggests that downloading the .Net installer wasn't able to finish and timed out. Are you in China or India
or are you behind any kind of firewall that may be blocking the network requests? If you are behind a firewall, could you work with your network admin to check if any related requests are blocked? In this issue dotnet/vscode-dotnet-runtime#1463 (comment), someone listed a few domains you may watch for.

You may also try tweaking the timeout value in the VS Code settings as suggested to see if it mitigates the issue for you after restarting VS Code.

[kvenkatrajan]

@nagilson - any thoughts or recent reports on timeouts? Is this something that will be fixed : .NET Runtime update timeout · Issue #1463 · dotnet/vscode-dotnet-runtime or has a workaround?

[nagilson]

This could also happen due to a proxy. If the user is using a proxy service or VPN they may need to add it in our settings. That is documented here:

https://github.com/dotnet/vscode-dotnet-runtime/blob/main/vscode-dotnet-runtime-extension/README.md#the-extension-thinks-you-are-offline-with-error-response-of-400-or-407-and-you-have-a-proxy

This was a bigger issue in the past but has largely been resolved -- a large part of it is also out of our control as it's the install scripts that use this website to download .NET, and then the issue was often with Verizon or whoever was hosting the CDN, who we chatted with extensively. The server host is changing pretty soon to be more internal (not part of our team), theoretically that would help but it could also have unknown issues which we will need to be weary of, such as how the Verizon CDN had a lot of issues with China and India.