I sincerely apologize for the server issues as of late.
Unfortunately, the instance is inaccessible until a reboot, which purges the logs that I might use to troubleshoot what was going on. I will hopefully have enough time this weekend to either dig into the issues or to set up some log aggregation to identify what might be causing the issues.
For the time being, I have upgraded the server again in the hopes that throwing some additional power at it might improve the stability.
Some better news, though, I’ve been working on setting up a copy of this in my homelab and testing out getting it accessible from the outside world. While I definitely don’t have as stable of an environment as AWS provides, I can throw a lot more server power at it without incurring a ton of costs and I already have monitoring and logging set up in my homelab to be able to troubleshoot issues more easily.
Again, I hope the server issues haven’t been too much of an inconvenience and I hope that in the near future I can provide a much more stable service to everyone.
Thanks again for your patience and for being a part of the community!
Agreed. In fact it’s had such problems that its content doesn’t even seem to be federating to my main instance anymore, likely because it’s been deemed “dormant.”
We’re also several versions behind and there have been major security fixes since then…