@olivierlambert No problem at all, it was my pleasure. I hope it helps other having the issue.

@florent I have installed the branch and that solves the problem

@florent From the XO side, yes I was testing that. I have added the key.

@florent No problem.

@florent I have created a new key that is bucket specific. I added the credentials but I assume I must need premium as it says feature unauthorised. I have already used the trial up. Not sure if that is an issue.

Do you need XOA connected to a xenserver? If not I don't mind leaving the tunnel open and you can take a look when you like.

There are a few test backups in the bucket, nothing I need.

@florent I have the free version of XOA as well as the XO from sources. I will add the B2 credentials to XOA.

I might be having the same issue, which only appeared when I updated XO. There appears to be an issue when you use a key that is specific to a bucket. If I use an key that has permission on all buckets you don't get the not entitled message, but obviously that is not ideal.

I have tested the bucket with the s3 aws tools and it worked without issue.

I hope this helps.