I have configured buckets and synced three joplin instances. One time it lasted a month. Another lasted a day. The most common error is *Got Metadata for Path but could not fetch content. * Anyone have any tips or tricks to getting this to work? I sure like concept, the best place to sync for me. And yes I can see the markdown file in the bucket so…
And Yes, I meant to put S3. DOH! Been working on this far too long today!
I know the error is basically, it can sync but cannot read the file. It finds the file. I can see the file.
I removed everything from the bucket, forced skip safe, and then reset it. So the bucket was empty, as verified by viewing it. Created a new notebook and a single note. Sync. Error returned. The file exists but it cannot read the content. If the app can make a file, it should be able to read the file.
Joplin for android, version: 2.11.32, databse v42
Reading through the error log now…
As far as I know, yes, it’s reliable and a lot of people are using it. Often they use the open source alternative MinIO which is compatible.
Only issue I would say is in terms of maintenance because unlike other sync targets, which I can usually fix, this one I have no clue about and any fix needs to come from other contributors who may or may not be around.
I appreciate all your work, I was reading the discussion on adding S3 as a sync option. Reading that made your reply here make a lot more sense, I didn’t realize you were commenting as a maintainer of the main branch.
So I guess the best thing I can do is try and discover where this error is occurring. Working with a clean bucket from the desktop (Linux client) appears to be working fine. So was it an IOS app or an Android app that is causing the issues? I made sure to completely purge the data and application on an android device, and will set that up next.
If I can find a specific repeatable cause I will revisit it on github.