1275 - FSR to Azure error: "An existing connection was forcibly closed by the remote host" Jolette Roodt 27 March 2020 08:48 Updated Follow Export as PDF Tags: Workaround FSR Azure Symptom While the user is attempting a test FSR of an account to Azure, a (403) Forbidden error is experienced because the user does not have the relevant permissions. This is resolved with some manual permissions changes. However, on the next attempt of a test restore, the following error is presented on the StorageServer multiple times: Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host. Cause This happens because the public IP of the device where the restore agent is running is not included in Azure's whitelist. Solution Add the IP address of the relevant device to the approved list in the Azure network resource. To do this: Open the storage account in Azure. Go to Firewalls and virtual networks. Tick the box Add your client IP address. Related articles 1234 - FSR to Azure limitations and troubleshooting 1284 - Warning shown if non-persistent paths are found in /etc/fstab 1224 - How to do a Full System Recovery to Azure 1231 - Limitations of FSR 1297 - ESE: Backup fails if Exchange has been removed from server Comments 0 comments Please sign in to leave a comment.