• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Question Cloudflare R2 as S3 backup

ralph22

New Pleskian
Server operating system version
CentOs 7.9
Plesk version and microupdate number
18.0.56 Update #4
Hello,
Anybody managed to setup Cloudflare's R2 storage inside Amazon S3 extension for a backup?

I've been using Dropbox ext. but it such a garbage I don't want to use it anymore. Constantly disconnecting and have to re-authorise it, at least every couple of days.

Cloudflare looks to be a nice alternative to S3 but I'm getting access error:
Unable to check bucket and directory existence. Make sure you are using correct IAM policy (400 Bad Request).

Not sure where to go next with this ^^
 
Backblaze B2 with the Amazon S3 extension works great:

 
Unable to check bucket and directory existence. Make sure you are using correct IAM policy (400 Bad Request).

@ralph22, it's been a couple of months since you posted this, so I hope you've been able to solve this. If not, and for other users with the problem, it might be useful to know that if you encounter this error, you'll need to omit the slash preceding your bucket name. So use my-bucket instead of /my-bucket.

Also note that the Plesk S3 extension doesn't cope well with paths that contain dashes (-).
 
Last edited:
Back
Top