this post was submitted on 20 Jun 2023
45 points (97.9% liked)

Selfhosted

40412 readers
253 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

Are there any Discord servers or somewhere in the Matrix to chat about hosting a Lemmy instance? I've got Lemmy running, but I think there are several of us in the same boat struggling with federation performance issues and it might be good to have some place to chat real time.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 10 points 1 year ago (3 children)

My server is struggling with federation. Pretty much everything I see in the logs with debug turned on is this:

2023-06-20T01:55:28.018419Z WARN Error encountered while processing the incoming HTTP request: lemmy_server::root_span_builder: Header is expired

[–] xebix 9 points 1 year ago (2 children)

This is exactly what I am seeing. I just tried upping federation_worker_count in the postgres database. I saw someone in another thread mention trying that so we’ll see.

[–] [email protected] 1 points 1 year ago

Check that your server time is synced to an NTP server and accurate. Federation requires the correct time.

[–] [email protected] 1 points 1 year ago

That guy was me, and it seemed like it worked. Those errors were flooding in, and when I changed the workers to 1024+, they practically stopped except every few seconds, which may not even be my server's fault.

[–] [email protected] 1 points 1 year ago (1 children)

There is an nginx setting you can tune as well. I believe it was worker threads? Can’t remember the exact one and too tired to ssh into my instance to check.

[–] [email protected] 1 points 1 year ago* (last edited 1 year ago)

This post says that the worker threads only effect outbound federation. I'm struggling with my instance not receiving anything inbound.

[–] [email protected] 1 points 1 year ago

Upping worker count significantly reduced those in my case. If Lemmy is maxing out your CPU too much though by chance, you may need to upgrade.