Fedia.io has 422 monthly active users - basically, 422 accounts have logged in within the past 30 days. I suppose I am comparing it to infosec.exchange, which has about 15000 monthly active users. I do believe that fedia.io is the most active mbin or kbin instance, by a factor of 2 or 3, but relatively quiet in comparison to Mastodon and Lemmy.
Hetzner makes their own servers in a form factor that works for their rack space. There are lots of YouTube videos on that. I don’t know specifically why these are failing, but being an old time engineer and knowing the CPU they are running, I am going to bet it has something to do with cooling. Either the main board is getting too hot (I monitor CPU temp and that seemed fine) or it is related to either vibration from the certainly larger CPU fan it needs, or somehow related to how the CPU impacts the power supply - possibly creating noise that ultimately burns out capacitors or something similar.
Apologies for having registrations closed. The moderation tools in Mbin/kbin are very very basic and I keep experiencing large numbers of spam signups, with no meaningful way to handle them until they sign up and start spamming
Which lemmy instance were you not seeing it on? One of the challenges with all fediverse applications (mbin, lemmy, mastodon, etc) is that posts and comments don’t federate with other instances unless someone on the other instance follows the person or the magazine.
I do not believe existing posts and comments will federate to a different instance after someone on that instance subscribes to the magazine. Only new posts and comments will.
That GitHub tracker is for problems with mbin code, not with instances running Mbin software. The problem that Fedia experienced is very likely caused by a bug of some sort in mbin (or something that Mbin is depending on), but we don’t know for sure what it is yet. Once I’m unemployed in a week, I hope to have more time to debug issues like this and get them resolved.
The cause is unclear to me, but the processes that manage incoming and outgoing federation were "stuck" until I manually intervened. It's running now. I'm adding to my to-do list for after my job ends in 10 days to implement some sort of detection and hopefully automated restart for when this happens again.
I'll open the back up. An issue with mbin is that there's no way to moderate new accounts, and so I have been battling massive amounts of spam, and the moderation interface for mbin is not super efficient, so it creates a LOT of work.