• Dear Pleskians! The Plesk Forum will be undergoing scheduled maintenance on Monday, 7th of July, at 9:00 AM UTC. The expected maintenance window is 2 hours.
    Thank you in advance for your patience and understanding on the matter.

Issue Unable to create the remote backup to s3: Transport error

Polsys

New Pleskian
Server operating system version
Ubuntu 20.04.6 LTS
Plesk version and microupdate number
Plesk Obsidian v18.0.64_build1800241008.13 os_Ubuntu 20.04
I have several servers with the same specs and the Backup to Cloud Pro+Amazon S3 Backup extension backing up to S3 seamlessly. However, one single server has problems with scheduled backups. For a few weeks, this is the error that has been found every day:

Code:
Unable to create the remote backup: Transport error: Extension transport: ext://s3-backup/subscription/4/: Error executing "PutObject" on "https://xxxxxx.s3.us-west-2.amazonaws.com/xxxxxx/"; AWS HTTP error: cURL error 6: Could not resolve host: xxxxxx.s3.us-west-2.amazonaws.com (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://xxxxxx.s3.us-west-2.amazonaws.com/xxxxxx/

The server has been running for years; this problem appeared a few weeks ago.

Manual backups to S3 work well with the same configuration; only the scheduled ones fail. Things I've done already:
  • Restarted services.
  • Restarted server.
  • Incremented values in panel.ini, following Resolved - Large backup to S3 fails with WARNING (no files uploaded)
  • Checked connectivity between servers with nslookup tests: all seems ok.
  • The bucket is located in the eu-west-3 region, and I've tried changing the default extension region in panel.ini (RegionForCustomEndpoint) from us-east-1 to eu-west-3 without success.
  • Restored panel.ini values to default, no changes.
  • Deleted backup extension and reinstalled.
One point I don't understand: in the backup settings, it is not possible to indicate the region of the bucket (eu-west-3, in my case). It seems panel.ini has a default value (us-east-1) and the script connection calls to us-west-2. I suppose Amazon automatically redirects any call to the correct region.

Any idea? Thank you.
 
Hey, @Polsys. Was the server up and running when you encountered the error? Do you have other scheduled tasks running alongside the backups?
 
Hi, @Sebahat.hadzhi. I noticed these errors through email alerts from the Plesk panel, so the server was running. Yes, I have several cron tasks running periodically on this server, some from Plesk, others from some extensions, and a few more from user scripts (none simultaneously as the backup task). All of them are triggering well.
 
Have you tried these settings in the panel.ini extension?
Code:
[ext-s3-backup]
SendRequestPayerOption = off
MaxResumeAttempts = 200 
MaxResumeFailures = 200
 
Have you tried these settings in the panel.ini extension?
Code:
[ext-s3-backup]
SendRequestPayerOption = off
MaxResumeAttempts = 200
MaxResumeFailures = 200
I tried, but nothing has been fixed (identical errors).
 
Is the domain resolvable from the server's console? Could it be a DNS error or a typo in the domain?
The bucket name is hidden for privacy. Note that manual backups are working correctly with the same configuration.

Bash:
nslookup xxxxxx.s3.us-west-2.amazonaws.com
Server:        127.0.0.1
Address:    127.0.0.1#53

Non-authoritative answer:
xxxxxx.s3.us-west-2.amazonaws.com    canonical name = s3-r-w.us-west-2.amazonaws.com.
Name:    s3-r-w.us-west-2.amazonaws.com
Address: 3.5.86.129
Name:    s3-r-w.us-west-2.amazonaws.com
Address: 52.218.230.57
Name:    s3-r-w.us-west-2.amazonaws.com
Address: 3.5.81.135
Name:    s3-r-w.us-west-2.amazonaws.com
Address: 52.218.133.26
Name:    s3-r-w.us-west-2.amazonaws.com
Address: 3.5.76.144
Name:    s3-r-w.us-west-2.amazonaws.com
Address: 52.92.197.42
Name:    s3-r-w.us-west-2.amazonaws.com
Address: 52.218.222.1
Name:    s3-r-w.us-west-2.amazonaws.com
Address: 52.218.250.113

Could the extension be configured to point directly to the bucket's region? This could mitigate the error connections.
 
Back
Top