(Boost for awareness of this shitty situation.)

IDrive's got some explaining to do.

I moved from Amazon S3 to IDrive e2, about a month ago.

Yesterday I found that my buckets became inaccessible, either through their GUI or through the web.

This means:

- No Mastodon cache.
- No offsite WordPress backups. (They still happen on site.)

I've reported the problem yesterday using a GUI feature, but truth be told, this did not seem to create a ticket. I've emailed them this morning, and got a reply that a ticket was created.

This is complete and utter shit. I was over one year with Amazon S3, and *never* had any problem.

One month with IDrive e2, and I run into this shit.

I'll try to move my bucket from one region to another, for higher availability on my storage provider ( -> ) . Today, this instance may be down for a couple of hours due to this. I'll use rclone on a server to sync bucket to a new one. Hopefully I won't break shit. Wish me luck!

I've cleaned up my Mastodon instance's headers and purged old assets, and woah, this is a huge cleanup.

The issue was, iDrive e2 had randomly started to give timeout errors on my api key, so I could not even browse the bucket with another client. I'm assuming it's due to having too much object in the storage.

The errors were like this:

> Net::ReadTimeout with #<TCPSocket:(closed)>

Here's some before and after:

Finally, got my first bill from Cloudflare R2 ... as they have no overview of the current running cost, this was interesting.
Storage is weirdly counted and not a problem at all... but my mastodon instance generated 2.5 million Class A operations for $9 last month. 3 days ago I moved to iDrive e2 - bc I hated that I have no clue about the running cost with Cloudflare. Idrive is 4$ for 12 months and that is it.

#mastodon #instance #cloudflare #clourflareR2 #idrive #idriveE2
#s3 #s3Storage

Recap on Mastodon instance storage:
- ZFS 5400rpm HDD: too slow with hundreds of thousands small files
- Storj: too expensive in the long run because of the segment fee($0.0000088)
- IDrive e2: timeouts on media upload 20% of time (over 1 minute object put time in some cases)
- Backblaze B2: works well and I will probably settle on it

Just got rid of that #s3 proxy container for my #idrive #idrivee2 storage to #cloudflare #cdn , thanks to @vito 's awesome guide for storage solution (for #mastodon ):

https://vitobotta.com/2022/12/25/storing-mastodon-assets-in-super-cheap-object-storage-idrive-e2/

The only difference is that I set the CNAME to assets.domain.com instead of wildcard one , but it still worked nicely!

You should definitely follow him as well! #mastoadmin

My instance will be offline for a couple of hours. I'll try to migrate to a #CDN solution for my assets, and keeping it offline while moving the data just in case. I'll move my assets to #idrive #idrivee2 , behind #cloudflare CDN, which is huge thanks to @vito who directed me through the correct way while I was lost! #mastoadmin

@g3rv4 Heya, thanks for reminding this! Never thought about #cloudflare #cloudflarer2 which has been in front of my face all along.

The pricing is still high comparing to #backblaze , #wasabi and #idriveE2 , however it's still cheaper than what I first had in mind. I'd rather pay premium for a stable service.

#mastoadmin sadly #backblaze b2 is banned in my country (most possibly for the stupidest reason the whole api domain got banned), so I'm looking for alternatives for #mastodon storage solution.

I've heard about #idriveE2 from #idrive . Has anyone used it, along with #cloudflare or similar CDN? How was your experience with #idrive #e2 ?

https://www.idrive.com/e2/

Or has anyone been using other storage solutions apart from #aws #s3 and #backblazeb2 ? E.g. #wasabi ?

https://micro.arda.pw/@arda/109463447161704765

Oh, I just remembered that I got 1 TB of #idriveE2 storage as well! I am gonna try that next if it works with #mastodon and #cloudflare. The first year is only $4 (yes, you read it right) and then $40/year which is cheaper than #Wasabi and #Backblaze. Also when I tested it it seemed very very fast. Gonna try it now..