#idrivee2 — Public Fediverse posts

Dude, IDrive e2 just did maintenance on the Singapore node without telling us! And their status page is behind a login. I wouldn't recommend them.

It's messing up our toots with images, so they're not posting or showing up.

#IDrive #IDriveE2 #S3

(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.

#IDrive #IDriveE2 #AmazonS3 #Mastodon #WordPress #S3

Well, pretty much fuck it!

The France region broke all my images and uploads were not working, but yesterday it was quite good.

I finally moved to #scaleway from #idrivee2 #idrive .

I was a customer of theirs already at 2016-2017, and I knew what I was going into.

Also their free tier for object storage is awesome, whopping 75 GBs, and after that, about 1 cent per GB per month.

The progress was breeze, and had no issues.

I simply had to alter my docker compose yaml like this though.

+

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!

#mastoadmin #idrive #idrivee2 #rclone

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:

#mastoadmin #mastodon #idrive #idrivee2 #s3 #tootctl

Download #iDriveE2 Frankfurt -> Hetzner Falkenstein

Nervig. Nachdem #iDriveE2 anfangs wirklich schnell war, ist das inzwischen unbenutzbar langsam. Teils nur noch 2MByte/s von Server ⇿ Server. Klar, dass das viel zu langsam für #Mastodon ist. Das Webinterface lädt sich auch gern zu Tode oder vergisst die Buckets.

Wieder ein S3 Provider von der Liste gestrichen.

Werde vorerst alles wieder lokal bei #Hetzner hosten.

#mastoadmin

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

#mastodon #storj #BackblazeB2 #backblaze #s3 #idrive #idrivee2 #zfs

Kopiere gerade 64GB von einem #S3 Dienst zum anderen. Dank #rclone ist das erschreckend schnell und unkompliziert.
Zumindest wenn man die --transfers hochstellt, die sind per Default=4.
--transfers={16,20,24,32,64}
Does the trick.

Warum? Meine Instanz hat den Cloudflare R2 recht voll gekloppt und da man kosten erst am Ende des Monats sieht, wenn alles zu spät ist, naja irgendwie mag ich das nicht.
Daher jetzt den 1TB #iDriveE2 für 4$ / Jahr

#mastodon #s3 #cloudflare #idrive

This is the 2 months of storage graph of my mastodon instance

Bucket size keeps at a constant level, which I believe depends on the number of followers (it also flushes the old images), so it has a constant flow, however, the number of headers is getting bigger than ever.

The new major version will possibly bring a fix for this.

#mastoadmin #s3 #idrive #idrivee2

@zaherg @vito is the real hero here. I stumbled upon him on blue bird site back then, he was also trying to put it together. I also struggled from here and there with idrive / cdn integration, but he created a nice guide to use the #idrive e2 with #cloudflare CDN:

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

Only side note: If you're a paid customer, you can enable public reads from the webui directly, or you could use a proxy container (which I have been doing for a while)

#idrivee2 #mastoadmin

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

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..