Deploying IronPDF NuGet Packages: Fixes

Curtis Chau

Updated: August 2, 2026

Download IronPDF

• NuGet Download
• DLL Download
• Windows Installer

• ---

• Start Free Trial

Copy for LLMs

• Copy for LLMs

  Copy page as Markdown for LLMs
  # Deploying IronPDF NuGet Packages: Fixes You might see one or more of the following error messages when trying to deploy a NuGet package: ```txt Failed to deploy NuGet package '_IronPdf.Native.Chrome.Windows(version)' ``` ```txt System.Net.WebException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. ``` ```txt System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ``` ```txt System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ``` ```txt System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host ``` ## Possible Cause The most common cause of these errors is related to outdated TLS protocols. As of April 2020, [NuGet has removed support for TLS 1.0 and 1.1](https://devblogs.microsoft.com/nuget/deprecating-tls-1-0-and-1-1-on-nuget-org/), and now enforces TLS 1.2. If TLS 1.2 is not enabled on your system, NuGet commands may fail. Switching from HTTP to HTTPS won't resolve the issue if TLS 1.2 is not enabled, as NuGet now requires secure connections. ## Solutions 1. **Install Visual C++ Runtimes:** Ensure that the [Visual C++ Redistributable for Visual Studio](https://visualstudio.microsoft.com/downloads/#microsoft-visual-c-redistributable-for-visual-studio) is installed on your system. Missing runtimes can cause issues with certain packages, including IronPDF. 2. **Update Visual Studio:** Make sure you are using a recent, up-to-date version of Visual Studio. **Visual Studio 2015 or higher** is required to properly support modern TLS protocols. - In Visual Studio, go to: - Tools > Extensions and Updates > Updates > Visual Studio Gallery - Update the NuGet Package Manager to the latest version. 3. **Enable Strong Cryptography in .NET:** If the above steps do not resolve the issue, you may need to enable strong cryptography in .NET. This can be done by modifying the registry. 1. Create a `.reg` file with the following content: ```txt [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319] "SchUseStrongCrypto"=dword:00000001 [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319] "SchUseStrongCrypto"=dword:00000001 ``` - The above registry entries enable the use of strong cryptography in .NET on both 32-bit and 64-bit versions. 2. Run the `.reg` file to update the registry settings. This enables strong cryptography in .NET, allowing TLS 1.2 connections. No reboot is required. After applying these changes, try running your NuGet command again. For more details, refer to this Stack Overflow post: [NuGet fails: The underlying connection was closed: An unexpected error occurred.](https://stackoverflow.com/questions/20445638/nuget-fails-the-underlying-connection-was-closed-an-unexpected-error-occurred) Reach out to us by submitting an [Engineering Request](https://ironpdf.com/troubleshooting/engineering-request-pdf/) should you need further assistance.

• ---

• Open in ChatGPT

  Ask ChatGPT about this page
• Open in Gemini

  Ask Gemini about this page
• Open in Grok

  Ask Grok about this page
• Open in Perplexity

  Ask Perplexity about this page

Share

• Share on Facebook
• Share on X (Twitter)
• Share on LinkedIn

• ---

• Email article

You might see one or more of the following error messages when trying to deploy a NuGet package:

Failed to deploy NuGet package '_IronPdf.Native.Chrome.Windows(version)'

Failed to deploy NuGet package '_IronPdf.Native.Chrome.Windows(version)'

System.Net.WebException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

System.Net.WebException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send.

System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send.

System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.

System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.

System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host

System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host

Possible Cause

The most common cause of these errors is related to outdated TLS protocols. As of April 2020, NuGet has removed support for TLS 1.0 and 1.1, and now enforces TLS 1.2. If TLS 1.2 is not enabled on your system, NuGet commands may fail.

Switching from HTTP to HTTPS won't resolve the issue if TLS 1.2 is not enabled, as NuGet now requires secure connections.

Solutions

1. Install Visual C++ Runtimes: Ensure that the Visual C++ Redistributable for Visual Studio is installed on your system. Missing runtimes can cause issues with certain packages, including IronPDF.

2. Update Visual Studio: Make sure you are using a recent, up-to-date version of Visual Studio. Visual Studio 2015 or higher is required to properly support modern TLS protocols.

   • In Visual Studio, go to:
     • Tools > Extensions and Updates > Updates > Visual Studio Gallery
     • Update the NuGet Package Manager to the latest version.

3. Enable Strong Cryptography in .NET: If the above steps do not resolve the issue, you may need to enable strong cryptography in .NET. This can be done by modifying the registry.

   1. Create a .reg file with the following content:

      [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319]
      "SchUseStrongCrypto"=dword:00000001
      
      [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319]
      "SchUseStrongCrypto"=dword:00000001

      Text
      • The above registry entries enable the use of strong cryptography in .NET on both 32-bit and 64-bit versions.

   2. Run the .reg file to update the registry settings. This enables strong cryptography in .NET, allowing TLS 1.2 connections.

No reboot is required. After applying these changes, try running your NuGet command again.

For more details, refer to this Stack Overflow post: NuGet fails: The underlying connection was closed: An unexpected error occurred.

Reach out to us by submitting an Engineering Request should you need further assistance.

Curtis Chau

Chat with engineering team now

Technical Writer

Curtis Chau holds a Bachelor’s degree in Computer Science (Carleton University) and specializes in front-end development with expertise in Node.js, TypeScript, JavaScript, and React. Passionate about crafting intuitive and aesthetically pleasing user interfaces, Curtis enjoys working with modern frameworks and creating well-structured, visually appealing manuals.

...

Read More