Search

EDIT: Looks like this is resolved now. For future reference, I had checked !support@lemmy.world, but I didn't think to check the announcements community, !lemmyworld@lemmy.world. I'll try to remember to check that space next time before posting. Thanks for chiming in, everyone!

ORIGINAL ISSUE:

I've noticed the last two game day threads on !caps@lemmy.world have not federated from my home instance (.ml) to either of the remote instances I've checked so far (https://lemmy.world/c/caps and https://lemm.ee/c/caps@lemmy.world).

The .ml posts' URLs are https://lemmy.ml/post/22823350 (from two days ago) and https://lemmy.ml/post/22885345 (from less than an hour ago).

The fact it's affecting multiple remote instances suggests that maybe there's some issue specific to .ml.

Searching recent support posts, I came across [this federation health checker site](https://grafana.lem.rocks/d/cdfzs0dwal3pca/federation-health-time-behind?orgId=1&var-instance=lemmy.ml&var-remote_softwa

Has anyone self-hosting Lemmy been able to federate with kbin instances? I subscribed to magazines on a few kbin instances (kbin.social, fedia.io and kbin.sh) but they do not push new posts to my instance, while Lemmy instances have no problem.

Is it a known bug in kbin or Lemmy? Is there an issue with my install (which is behind a reverse proxy and WAF)? Is it a "feature" in kbin to stifle competition?

Update #1: I have been made aware (thanks @stu@lemmy.pit.ninja and @meldrik@lemmy.wtf!) of a recent fix in the nginx config, but I don't think that's it: when looking at my reverse-proxy's logs, I don't even see any POST requests made to the inbox from kbin instances, so I believe they don't even try to push updates to me.

Update #2: Updating to Lemmy 0.18.1 resolved the issue!

So I'm currently trying to set up an instance, and I'm unable to upload pictures. The following toaster appears: https://imgur.com/d0MUhUb

And in the logs I see this:

 undefined

    
2023-06-25T10:48:11.127198782Z 2023-06-25T10:48:11.127080Z  WARN lemmy_server::root_span_builder: Request error: error sending request for url (http://localhost:8080/image): error trying to connect: tcp connect error: Address not available (os error 99)
2023-06-25T10:48:11.127262799Z Reqwest(reqwest::Error { kind: Request, url: Url { scheme: "http", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("localhost")), port: Some(8080), path: "/image", query: None, fragment: None }, source: hyper::Error(Connect, ConnectError("tcp connect error", Os { code: 99, kind: AddrNotAvailable, message: "Address not available" })) })

  

I have a pictrs container up, and set the following options in lemmy.hjson:

 undefined

    
  pictrs_config: {
    url: "http://pictrs:8080"
    api_key: "apikey"
  }

  

Also tried it w