jerry

The server fedia.io had been running on started developing stability problems overnight from Thursday April 4 to Friday April 5. By Saturday (today), the system was completely unbootable. After attempting to resolve the hardware issue with Hetzner (the ISP) for about 6 hours, I gave up and moved the site to a new server. All that took quite a lot of time, during which fedia.io was not available. My apologies for this.

Fedia.io is now running on it's own stand-alone server. This server is costing me $210/month, so any contributions are welcome. Please let me know of any issues.

I am going to be rehoming fedia.io to a new server. Today, fedia.io runs on shared app server and shared database server. I will be moving fedia.io to a dedicated 48 core/96 thread AMD epyc server with 256GB of RAM, which will house both the app and the database. This is less about fedia.io and more about the other apps running on the existing servers are that suffering due to performance issues with the mbin application, particularly the database queries. (Note: this isn't a slam on mbin - it just needs more optimization, plus fedia.io is a pretty busy server).

You have no doubt noticed that federation is breaking again. I am painfully aware of it. The issue is with the symphony queue runner that processes incoming messages from other instances. Occasionally, the server receives a message that causes the queue runner to die. I have to manually remove the offending message out of rabbitmq. The message does not appear to be malicious, rather there is something malformed in an otherwise legit looking post that causes the queue to die. I am working with the mbin team to track down what it is about the messages that causes the problem, but sadly until I there is a fix, this is going to keep happening

Hi all. I was recently made aware that people have been getting error 429's and other error 500's when visiting fedia.io. My hope/expectation is that those will no longer happen now that I've moved back to a bare metal install, but if you do experience that, please comment below, or if that doesn't work, send me an emai to jerry@infosec.exchange.

Thank you!

Hi all. It took a while for me to get to it, but I have just completed rehoming fedia.io from containers back to a bare metal install. This should fix the issue with federation stopping. I'll keep an eye on it, though.

Hello. I will be taking fedia.io offline on Saturday, Feb 3 to rehome it to a different server. Since moving fedia.io to a container-based platform, federation has been very unreliable and slow. I'll be moving to a non-container-based/bare metal install, which should address the federation issues.

Hi all. I am going to be taking fedia.io offline for a bit today to move to a new server, switch to a containerized version, and some other enhancements. Thanks for patience.

I was happily working on a different set of servers when apparently the database server for fedia.io became unresponsive. Once I realized it, I forced a reboot and everything is back to normal. Now that the code and database are stable(ish), I will be moving the site to actual server hardware in the coming days while I have some vacation time.

Hello everyone. I will be taking fedia.io offline in a few hours (timing dependent on work meetings) to apply the latest mbin updates, which should, among other things, fix 2FA.

In the coming days, I will be making a few other changes to improve the performance of the instance, moving the instance behind a CDN.

I spent an incredible amount of time over the past few days unf*cking the fedia.io database. It should be clean now and that should both dramatically improve performance and fix all or most all of the remaining error 500’s