When attempting to connect to an R2 bucket within Cloudflare as a Remote, it won't connect. I have successfully connected to an R2 bucket using an S3 compatible function within Plesk and other solutions. Errors don't really seem to make sense, however I know that the requirement for the bucket name is to NOT have a pre "/" at the beginning otherwise it doesn't recognise it. This was the workaround I had to do for Plesk. XO seems to automatically add the "/" regardless of whether I've put it in or not.
If you use XO from the sources, there's no stable release. As per our documentation, please use the latest commit available.
Have you tried without entering the protocol before? Directly the URL of the S3 provider
We only support AWS officially (more provider later). Until then, it's better to report on the forum first in this category: https://xcp-ng.org/forum/category/21/backup See you there!
Are you using XOA or XO from the sources?
XO from the sources
Which release channel?
stable
Provide your commit number
8b7e1
Describe the bug
When attempting to connect to an R2 bucket within Cloudflare as a Remote, it won't connect. I have successfully connected to an R2 bucket using an S3 compatible function within Plesk and other solutions. Errors don't really seem to make sense, however I know that the requirement for the bucket name is to NOT have a pre "/" at the beginning otherwise it doesn't recognise it. This was the workaround I had to do for Plesk. XO seems to automatically add the "/" regardless of whether I've put it in or not.
Error message
To reproduce
1.) Log in to XO 2.) Under Settings/Remotes create a new S3 remote and enter details 3.) See screenshots for addition information
Expected behavior
S3 Plugin should be able to cater for connections for R2, perhaps without automatically introducing a "/"
Screenshots
Node
18.20.0
Hypervisor
XCP-ng 8.2.1
Additional context
No response