A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
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)
Oh nice, that’s better than my solution. Less risky than downgrading.
That worked! Thanks so much to both of you :) Such a small change was driving me crazy
This is a change with 0.17.4. You cannot have both federation enabled and the private instance box checked. You might try downgrading to the 0.17.3 image (so that you can get into the UI) and unchecking either the private or federation boxes (whichever way you wanna go). I’d also suggest pinning the docker image versions, as I bet you’ve got latest set (or nothing set, which I believe also grabs latest), and the vm reboot prompted docker to go grab the latest image on startup. Surprise upgrades probably aren’t what you want.