FSR to Azure error An existing connection was forcibly closed

 Let us learn more about the error FSR to Azure error An existing connection was forcibly closed. With the support of our Server management support services, we can give you a complete solution to deal with the error.

Symptoms for FSR to Azure error An existing connection was forcibly closed: Symptom

Because the user does not have the necessary rights, a (403) Forbidden error occurs while performing a test FSR of an account to Azure.

We can fix this by making some manual permissions modifications. However, on the second test restore attempt, the StorageServer displays the following error message many times:

Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host.

Causes for the error

The FSR to Azure forcibly closed error occurs because the public IP address of the device on which the restore agent is executing is not on Azure’s whitelist. The error “An existing connection error” can occur when attempting to connect to an Azure service. Or it will happen when a resource using a Fault Tolerant Heap (FTH) mode-enabled FastCGI Process Manager (FPM) connection. And many other issues can cause to trigger the error.

How to solve the error?

Follow the steps given below as the solution to the FSR to Azure forcibly closed error:

In the Azure network resource, add the IP address of the required device to the permitted list. To accomplish this:

1. Firstly, create an Azure storage account.
2. After that, go to the Firewalls and Virtual Networks section.
3. Finally, check the box that Includes the client’s IP address.

[Need assistance with similar queries? We are here to help]

Conclusion

To sum up, the error FSR to Azure error An existing connection was forcefully disconnected is an easy fix. With the support of our Server management support services, we have now gone through the solution to the error.