Hi all! I was toying with installing Lemmy on my home server and some unused domain I had and finally did it, using docker compose. The server have all outside incoming ports closed except the explicitly open ones, don’t know if this could be related to my problems (for the lemmy instance only 80 and 443 are opened).

The instance generally works (reachable at wodri.com) but there are some problems:

  1. Frequent and random “AbortError: Aborted” banners on the UI when making some action. Usually fixed by just doing the same again.

  2. It fetches the communities from other instances if I search explicitly for them and I can see most of the threads from those communities, but usually with none or 99% of the comments missing on each external thread.

On the lemmy docker logs I see many invalid queries like:

lemmy_1 | 2023-06-27T11:08:01.196180Z WARN lemmy_server::root_span_builder: couldnt_find_object: invalid query lemmy_1 | 0: lemmy_apub::fetcher::search::search_query_to_object_id lemmy_1 | at crates/apub/src/fetcher/search.rs:19 lemmy_1 | 1: lemmy_apub::api::resolve_object::perform lemmy_1 | with self=ResolveObject q: “lemmy_support”, auth: Sensitive } lemmy_1 at crates/apub/src/api/resolve_object.rs:21 lemmy_1 | 2: lemmy_server::root_span_builder::HTTP request lemmy_1 | with http.method=GET http.scheme=“http” http.host=wodri.com http.target=/api/v3/resolve_object otel.kind=“server” request_id=4bd1501c-a286-43f1-86ee-34f5b7444f8b lemmy_1 | at src/root_span_builder.rs:16 lemmy_1 | LemmyError { message: Some(“couldnt_find_object”), inner: invalid query, context: SpanTrace [{ target: “lemmy_apub::fetcher::search”, name: “search_query_to_object_id”, file: “crates/apub/src/fetcher/search.rs”, line: 19 , { target: “lemmy_apub::api::resolve_object”, name: “perform”, fields: “self=ResolveObject { q: "lemmy_support", auth: Sensitive }”, file: “crates/apub/src/api/resolve_object.rs”, line: 21 }, { target: “lemmy_server::root_span_builder”, name: “HTTP request”, fields: “http.method=GET http.scheme="http" http.host=wodri.com http.target=/api/v3/resolve_object otel.kind="server" request_id=4bd1501c-a286-43f1-86ee-34f5b7444f8b”, file: “src/root_span_builder.rs”, line: 16 }] }

  • hawkwind@lemmy.management
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    Not sure about the abort banners. The remote communities behaviour sounds perfectly normal. The resolve object error could be related to your instance trying to pull content from another.

  • ℍ𝕖𝕝𝕚0𝕤
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    1
    ·
    1 year ago

    If you just installed from lemmy-ansible, you must be running version 0.18 but a lot of big instances are still on 0.17.4. Do you also have this behavior when subscribing to communities hosted on 0.18 instances like lemmy.ml ? I found that federation is mostly broken from 0.18 to 17.4.