Selfhosted @lemmy.world sum_yun_guy @lemmy.world 1y ago

Lemmy selfhost error | getaddrinfo EAI_AGAIN lemmy

Hi all,

I did originally have this working no problem, until I rebooted my vm. Now I get this error when trying to access the site in all browsers:

404: FetchError: request to http://lemmy:8536/api/v3/site? failed, reason: getaddrinfo EAI_AGAIN lemmy

When I check out the docker-compose logs, I see this:

Error: LemmyError { message: Some("Cannot have both private instance and federation enabled."), inner: Cannot have both private instance and federation enabled., context: "SpanTrace" }

Can anyone point me to where I need to be looking please?

Thanks!

5 comments

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)
- That worked! Thanks so much to both of you :) Such a small change was driving me crazy
- Oh nice, that’s better than my solution. Less risky than downgrading.
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.