#idrivee2 — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #idrivee2, aggregated by home.social.
-
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.
-
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.
-
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.
-
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.
-
(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.
-
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!
-
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 -
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 -
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#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 -
@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.