this post was submitted on 16 Apr 2024
16 points (90.0% liked)

Fediverse

17735 readers
54 users here now

A community dedicated to fediverse news and discussion.

Fediverse is a portmanteau of "federation" and "universe".

Getting started on Fediverse;

founded 5 years ago
MODERATORS
16
submitted 7 months ago* (last edited 7 months ago) by [email protected] to c/[email protected]
 

Sometimes I click on instances to check them out, but feddit.de has consistently been returning a 500 error however there are people posting from there. What kind of magic is this? Have the Germans figured out how to have a private instance that's somehow still connected to the fediverse?

https://downforeveryoneorjustme.com/feddit.de says it's down

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 15 points 7 months ago* (last edited 7 months ago) (5 children)

The web-UI and Pictrs image host has been down for more than a week now, but the backend API for app use and federation was still working. ~~But I have the feeling that sometimes during the last 24h that also went down, or at least I haven't seen a post relayed from them during that time.~~

I really don't know what's going on there, but at least initially someone said they ran out of storage on their server. But it seems odd that this takes more than a week to fix. Maybe the main admin is on holidays?

[–] [email protected] 5 points 7 months ago* (last edited 7 months ago) (1 children)

As wgbirne already said, the admin has more important real life stuff to do unfortunately. If I understood it correctly, the lack of storage also killed the database, leaving it in an inconsistent state. In addition to that there seems to be an issue with the backups so no easy rollback and probably a lot of manual fixing needed.

[–] [email protected] 1 points 7 months ago

Ugh, that will be a pain to fix indeed then. Makes it much more understandable that they take their time with it, but hopefully they also fix their backups.

load more comments (3 replies)