Luckily we have mirrors and these were not affected....

Luckily we have mirrors and these were not affected. We grabbed a new machine somewhere else (Scaleway ; if we name-and-shame the one we might as well name-and-greet the other) and immediately started re-importing our data to our new Master server.

All in all, it still took about 48 hours to get these 8-ish TB back online.

Like 9 December at 9:15 | Open on mastodon.social

5 comments

Kiwix

If there is any silver lining to this, it is that we could see a few points of vulnerabilities as well as our ability to turn things around in a reasonably quick manner (here be kudos for the two heroes who manage our infra).

Learning were made, and we will see in the coming weeks/months how we can implement new safegards within our resource constraints.

/END

9 December at 9:15 | Open on mastodon.social

Joachim

@kiwix

Huh, thanks for sharing. That was a though time, eh? :-(

On slightly lighter note: most of your user should have had the content they wanted allready - localy and #offline. (That _is_ the point of #kiwix, right ? )

9 December at 9:28 | Open on literatur.social

T.J. Crowder

@kiwix Good golly. I've been using Hetzner for years and even just recently recommended them. Sorry you've had this trouble. I'd be really curious to know what their reason was. (Lost email or no, someone or some system _must_ have a record of why they took such a draconian action.)

9 December at 11:10 | Open on hachyderm.io

Kiwix

@tjcrowdertech Yeah we've moved on now and are a bit sad about the whole thing, but it would be nice to know at some point and get closure.

9 December at 11:28 | Open on mastodon.social

Dan Jones

This is the second "don't use Hetzner" post I've seen this morning, and for somewhat different reasons.

Here's the other one.

@tjcrowdertech@hachyderm.io @kiwix@mastodon.social

9 December at 13:20 | Open on microwords.goodevilgenius.org

Go Up