Easy one to miss! The documentation isn’t very detailed. 🙂

What is your domain set to?

Also I think the !selfhosted@lemmy.world community might be a better place to ask for help.

That’s most definitely a bug, in my opinion. Might want to file an issue on GitHub.

Neat! I’ll definitely check this out.

Oh, good idea! Whatever works for you. I spent several hours yesterday trying all sorts of networking hacks to resolve the issue on my instance. I eventually found a combination that worked for me.

The concern here is we are all solving this issue in slightly different ways on our self hosted instances. Eventually, I hope the lemmy dev team releases 0.18.1 fixing all these issues for good.

One other thing I did was update my resolve.conf so that valid DNS IPs were making it to the containers. Otherwise the containers might not have valid DNS. Also try rebooting your host.

Here is what I did to fix the container DNS lookups failing:

https://stackoverflow.com/questions/20430371/my-docker-container-has-no-internet

Oh, this span builder error. Yeah I’ve been seeing that error since I upgraded to 0.18.0. Sorry, I don’t have a solution for this one.

Glad you figured out your pictrs error though! One other thing I did was update my resolve.conf so that valid DNS hosts were making it to the containers. Also try rebooting your host.

Feel free to add to this discussion. https://github.com/LemmyNet/lemmy/issues/3314

Yay! Thank you for confirming

Yay! Small victories

Are you running lemmy 0.18.0? It breaks a bunch of internal network connectivity. The short term solution is to add an external network to both the lemmy-ui and pictrs containers, then you can change http://pictrs:8080 to http://your_domain.

Note: there are also some issues in 0.18.0 with comment federation at the moment. Please reply to confirm this comment was seen, thanks!

You can load the project directly in GitHub and do a diff between 0.17.4 and 0.18.x.

Here are the diffs (0.18.0 vs 0.17.4)

• lemmy-ui
• lemmy backend

Awesome! Thank you for posting this. I will be updating my instance as soon as I can.

But on the other hand, look at how much the lemmy and kbin user base has grown. The blackouts had a significant impact in increasing lemmy adoption and usage.

Prior to the announced blackouts, I had no idea Lemmy even existed. Now here I am running my own instance.

Also, advertisers Reddit sells to have halted their campaigns until “next week.”

I think while on the surface it might feel underwhelming, it had more impact than you think. And now mods are discussing extending the blackout too.

Good question. I don’t know. Hypothetically speaking, if the parent instance of the community changes the relevant data in the database to another instance, would federation take over and automatically propagate the change? 🤷🏻‍♂️

Sounds like an interesting experiment at least, or a possible major bug waiting to happen.

Nice work! This will be convenient. Will try it out.

Technically you could fork lemmy-ui and make it a native feature and see if it gets accepted/merged back in. 😄

What a great write up! I think your description of what will happen is spot on.

Oh that’s interesting. So it was actually that your post was too big?

I’m not familiar with unraid.

I used the documentation over on join-lemmy.org to setup my instance, on ubuntu. main docs: https://join-lemmy.org/docs/en/administration/administration.html

Here are the docker specific instructions: https://join-lemmy.org/docs/en/administration/install_docker.html

It won’t post if you don’t select a language. That was my experience at least. If I left it unselected I’d get a forever loading icon when trying to save the post.

Curious to know what instance you are on?