Skip to main content

Backup Destination is Showing a Timeout Error.

Sean Huddy
  • Updated

Symptoms

When attempting to validate a remote backup destination you may see an error such as:

Error Validation for transport “YourBackupDesintationName” failed: Could not upload test file: Timeout 

You may also see a similar error when your backups are being transported to the remote destination.

[2020-08-15 02:35:56 +0000] warn [cpbackup_transporter] Upload attempt failed: Timeout at /usr/local/cpanel/3rdparty/perl/530/lib/perl5/5.30.0/Net/FTP.pm line 857.
 at /usr/local/cpanel/Cpanel/LoggerAdapter.pm line 27.

 

Description 

If you are seeing a timeout error when validating or transporting to your backup destination, the first place to look will be the timeout for the destination. The default timeout setting is 30 seconds. This may not be enough time for the connection to validate or the backup to be transported to the remote destination.

Here are the details for the timeout field

Timeout
  • Required — The maximum amount of time, in seconds, that you want the server to wait for a response from the remote server before it generates errors.
  • You must enter a number between 30 and 300.
  • If the server does not respond before the time expires, it makes two additional attempts to contact the server.
  • If the server does not respond after those attempts, the system administrator receives an email that notes the failed attempts. The system will retry the transfer when it runs the backup process again.

You can find more information on all of the settings in our documentation.

Backup Configuration » The Additional Destinations tab

 

Workaround

The workaround for this is to increase the timeout value in the settings for your Additional Destination.

  1. Navigate to WHM's "Backup Configuration."
  2. Click on the "Additional Destinations" tab.
  3. Next to the desired destination, click "Edit."
  4. Look for the "Timeout setting" and increase the value to "300."
  5. Click the "Save."

 

Related articles

Comments

0 comments

Article is closed for comments.