Easy one to miss! The documentation isn’t very detailed. 🙂
Easy one to miss! The documentation isn’t very detailed. 🙂
What is your domain set to?
Also I think the [email protected] 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.
As a Performance Engineer myself, these are the kind of performance improvements I like to see. Those graphs look wonderful. Nice job to all.
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
I turned that off, as well as show online status, years ago.
You should disable tracking everywhere you can. Opt-out of personalized ads. Enable the do not track feature.
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!
Commenting to bookmark this for future reference! Great write up. I’ll likely try this on my instance at some point.
Also testing to see if my comment shows up…
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)
Awesome! Thank you for posting this. I will be updating my instance as soon as I can.
That’s how I believe federation works. So everything I’m subscribed to with my user on my instance is pulled in and kept in sync. If the origin instance of the community goes down, everything that was synced up to that point still exists on my instance and I can read it.
Are we allowing emojis here?
You need permission to use emojis? 🤔
Oh, you mean in the sense that “emojis = downvotes” on Reddit. I still used them on Reddit anyway. 🤷♂️
BTW: you can use : shorthand for emojis, in case you didn’t know. 👍
It’s a bug. One of many related to how the UI updates in real time using websockets. The good news is they are getting rid of websockets in the next release, and should fix a lot of these issues.
https://github.com/LemmyNet/lemmy-ui/issues/1093
@[email protected] maybe a featured/sticky post pointing to currently open issues in GitHub would be helpful?
Is there anything Grafana cant do?
I have so many things pumping data “into” Grafana these days I’m surprised they haven’t tried to force me to pay for an enterprise license.
Anyway, thanks for sharing these, @[email protected]. As a performance engineer, I love to see this level of detail and commitment on your part to keep the user experience for lemmy.world at acceptable levels.