It looks like you may have gotten hit by this issue.

Since you’re already logged in on a client, you could try setting an email address (if not already set) and doing a forgot password. That should allow you to reset your password to one within the limit.

Feel free to reach out if that doesn’t work or you continue to have issues!

Community creation is currently disabled. If you have an idea for a new community, feel free to DM me and I can help you get set up.

This issue should be fixed now. Let me know if you continue to see any issues.

For the technical details:

Pictrs is used for managing images in Lemmy. It uses a Sqlite database on the local filesystem which limits its scalability. After a recent upgrade, it does now support migrating this data into Postgresql. I’m hoping to schedule some time soon to perform the update. This will allow multiple instances of Pictrs to be run in parallel providing better uptime and recovery.

What happens here is that the service gets into a bad state and it tries to bring up a replacement. But due to the local DB, the replacement is unable to get a lock on the filesystem and crashes. Once we switch it to use Postgres, this should no longer be an issue.

For now it’s open, but may change in the future to only special requests.

I would recommend looking for a server that might be related to your community. That way there’s better discoverability and support to help foster it’s growth. You can still add yourself as a moderator from lemmus for backup or ease of use.

Feel free to use whichever method you prefer! The only ask is to avoid directly uploading porn to lemmus. This is due to the limited moderation controls currently in-place and preferring to avoid the legal risk.

As for costs, while our bills are a bit high right now almost all of it comes from database and compute. Storage and bandwidth are pretty cheap for us and we aggressively cache everything we can.

Hey! Apologies for the delay, I only just noticed this message.

I believe the issue has been resolved. Please let me know if you’re still experiencing issues with this or anything else.

The underlying problem was that the endpoint wasn’t getting properly routed by the CDN. I’ve updated the configuration to fix this oversight.