Does your docker network setup have the lemmy server on an internal network with no external access? The default docker config is setup that way and caused what you're describing for me. Fastest fix is comment out the "internal: true" from the docker compose file, but you may want to consider the security implications of that.
this post was submitted on 07 Jun 2023
2 points (100.0% liked)
Lemmy Support
4655 readers
21 users here now
Support / questions about Lemmy.
founded 5 years ago
MODERATORS
this one? https://ohaa.xyz/u/0KjhJc.png
Yeah. Did you down and up the docker and see if the issue is resolved?
trying that right now
same error after modifying the file and recreating the container
Restarted and recreated the container and the host. still nothing
Not sure then, sorry :/
I have the exact same error with the ansible playbook