spanishla.blogg.se

"msg": "Cannot contact s3 service (bucket cloud-personal), will retry in 1s", I have no idea if this worked under Cells I am still getting the same error with that config applied ".personal": " That’s a bit weird, isn’t it? The pydio.json configuration file does not seem to allow selecting the signature version, and nothing on the official documentation refers to it. So, it seems that Cells is correctly configured to accept only V4 authentication for its own datasources, but it fails to connect with V4 authentication when mounting external datasources? The documentation for this is very straightforward and doesn’t go into details. It has no problems connecting to Cells via V4 authentication, but throws an (expected) error using V2. I suspected as much when doing some tests in the distant past, but today I experimented with the popular, generic s3cmd Python-based command-line tool to access remote buckets. Interestingly, when trying to connect to Cells using its own S3 API, it seems that only V4 authentication is supported.

Google Cloud apparently still supports V2 authentication - although they seriously encourage the upgrade to V4 - and that might be the reason why I had no problems with their connection. I haven’t tested Backblaze yet, but it’s quite clear that they only support V4 authentication, as do most of the providers I have been playing around with.

To clarify: I personally cannot afford any S3-compatible cloud storage (alas…) for the amount of data I have on Cells however, I’m constantly experimenting with whatever kind provider is happy to give me a free trial, and see how well such providers will integrate with the rest of my complicated setup

I’ve encountered the same error when trying to add a ‘new’ S3-compatible storage, but an ‘old’ existing connection Google Cloud S3-compatible storage wasn’t affected. Have tried upping the memory on the XO machine, but in all honesty it doesn't hit that too badly, it's just the upload to B2 that has this 2min timeout issue.Interesting. The test of the S3 config (little doctor's bag) comes back fine, but once we start a backup running it fails with "TimeoutError: Connection timed out after 120000ms". We've got a similar but different problem with B2.