this post was submitted on 09 Jun 2023
10 points (100.0% liked)
Lemmy Support
4656 readers
16 users here now
Support / questions about Lemmy.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Check the logs, if you see something about http error for lemmy.ml then the issue is the internal network.
Add a 3rd network just like the one for the proxy and add it to the lemmy container.
What happened to me was caused by this, the lemmy container couldn't connect to the internet so it wasn't able to find the other instances.
I think you might be on to something. I looked up myself(@tekeous@beehaw.org from apollo.town and got the following:
I'm not too familiar with docker networks - how would I add a third one?
So you want to have this:
And in the container this.
(leave the rest as is, you can name the new network however you want)
You're a bloody genius, thank you, that appears to have solved the problem.
Nice! This confirms it, I'll check tomorrow to share this in the repo to update the documentation.