Hi!
Hi!
I'm trying to migrate a bucket from Scaleway to R2 and I keep hitting the "The connection cannot be verified. Check the following and try again." message.
As far as I can see I've set all the parameters correctly (endpoint, bucket name, API keys) and the source bucket is set to Public.
Does anyone have any prior successful experience with Scaleway -> R2 migration and if so, is there anything special that needs to be done?
13 Replies
Hey there, we have a fix going out soon for some of the S3 compatible APIs. I can update you here when it is live and you can give a retry.
Hey, that would be great! Thanks!
@Valeriu Paloș the fix is now live! Would you mind trying your migration again?
Fair warning, Scaleway is not a provider we have explicitly tested with, but I took a peek at their documentation and it looks like it should work.
Understood.
I'll try.
It works!
Thank you!
Woohoo! Let me know if you run into any other issues.
Wow! The speed on this thing is... something else!
Nicely done!
That's fine with me 👍
Migration successful!
Actually, it finished yesterday (quite fast), but with some errors.
I tried it twice just to make sure (this shows the 2nd run), but still got errors.
Here's one of them for example.
I suspect something related to special characters in the file names... (not just diacritics, symbols as well: +, #, etc.); but I really don't know.
I solved it using a separate
rclone as @Space recommended:
rclone copy scaleway:<src> r2:<dest> --progress --size-only
Note that I had to use --size-only since otherwise rclone would track the modification time, which I think is not carried-over by the migration process, which would cause it to copy everything all over again.
Hope it helps.It looks like most of the failures received a 403 status code from the source bucket when we attempted to get the object. For some extra data, did you use the same credentials for the rclone migration as the super slurper migration?
Definitely could be something with the special characters, but I would expect something other than a 403 if that were the case. We'll look into it regardless and thank you for the feedback!