I also just recently switched to https://purelymail.com after hosting my own for several years via Mailcow and a cheap VPS. The cheap VPS was more expensive than the $10/year for Purelymail and I was only using it for mail anyway. Nothing to maintain now and so far very happy with how easy it was to move everything over.

Also, they don’t charge extra for additional domains so if you have multiple it’s still $10. Only been with them a few weeks so can’t say much yet for long term, but great so far!

I’ve noticed something similar on my instance in some cases as well. Nothing obvious logged as errors either. It just seems like the comment was never sent. In my case cpu is minimal so it doesn’t seem like a resource issue on the receiving side.

I suspect it may be a resource issue on the sending side. Potentially, not able to keep up with the number of subscribers. I know there was some discussion from the devs around the number of federation workers needing to be increased to keep up, so another possibility there.

It’s definitely problematic though. I was contemplating implementing some kind of resync this entire post and all comments via the Lemmy API to get things back in sync. But, if it is a sending server resource issue, I’m also hesitant to add a bunch more API calls to the mix. I think some kind of resync functionality will be necessary in the end.

I was just thinking about doing something like to migrate some of my communities over (and was even planning on writing it in Python). Just ran it and it worked perfectly. Thank you, this saved me a bunch of time!

I ran into this at one point as well. You can unset the private instance flag manually in the database and restart to get up and running again.

First connect to psql:

docker-compose exec postgres psql -U lemmy

Then run an update to unset the flag:

lemmy=# update local_site set private_instance = false;

Which should update 1 row (only 1 row in that table if you’re on a typical install)

I usually DIY and repurpose my old PC into a server when I upgrade. My current NAS is running on a ~10 year old i5 2500k in a (large) mid tower case packed with drives. It runs Unraid and also hosts a bunch of Docker containers for Plex, etc.

It’s definitely more work to set up than a pre-built and also more power hungry, so that’s the trade-off for the additional flexibility and lower cost of entry (at least in my case since it was mostly parts I already had). I am running low on expansion room since the 6 HDDs and 2 SSDs have about maxed out my case, but you’ll run into that same problem with pre-builts depending on how you size it.

I just switched to Kopia and B2 a few months back and it is working great so far. I backup my machines with Kopia to a local Unraid box on my network running Kopia server. Then the Kopia repo on the Unraid box is synced up to Backblaze B2 nightly.

I’m only backing up around 200 GB of data so the B2 storage is something like $1 a month.

That’s great, glad to see progress on simplifying deployment!