Hi all. I just setup a new install from scratch on FreeBSD (write up to come once I work out all the issues) but I can’t seem to subscribe to remote communities.
I’m running the backend and UI versions 0.17.4 and you can see the instance at https://discuss.petersanchez.com
Anytime I try to search for any community (ie, !lemmy_support@lemmy.ml) it says not found. Logs show errors about values, etc. I try via full URL or via the local instance url (`/c/lemmy_support@lemmy.ml) and it’s the same. I was able to subscribe to 1 remote community but about 10 others fail to be found.
Here’s an example of an error from the logs:
2023-06-30T00:10:30.187507Z ERROR HTTP request{http.method=GET http.scheme="http" http.host=discuss.petersanchez.com http.target=/api/v3/ws otel.kind="server" request_id=bfe8111b-8a78-4bc8-8e04-d4a91ff08837 http.status_code=101 otel.status_code="OK"}: lemmy_server::api_routes_websocket: couldnt_find_object: error decoding response body: missing field `properties` at line 1 column 158
0: lemmy_apub::fetcher::search::search_query_to_object_id
at /home/lemmy/.cargo/registry/src/index.crates.io-6f17d22bba15001f/lemmy_apub-0.17.4/src/fetcher/search.rs:17
1: lemmy_apub::api::resolve_object::perform
with self=ResolveObject { q: "!lemmy_support@lemmy.ml", auth: Some(Sensitive) }
at /home/lemmy/.cargo/registry/src/index.crates.io-6f17d22bba15001f/lemmy_apub-0.17.4/src/api/resolve_object.rs:21
2: lemmy_server::root_span_builder::HTTP request
with http.method=GET http.scheme="http" http.host=discuss.petersanchez.com http.target=/api/v3/ws otel.kind="server" request_id=bfe8111b-8a78-4bc8-8e04-d4a91ff08837 http.status_code=101 otel.status_code="OK"
at /home/lemmy/.cargo/registry/src/index.crates.io-6f17d22bba15001f/lemmy_server-0.17.4/src/root_span_builder.rs:16
I can access my users json details with curl -H 'Accept: application/activity+json' https://discuss.petersanchez.com/u/peter just fine.
Here is my nginx config:
https://paste.sr.ht/~petersanchez/2bd686389f7d0bdd5e8645fcedbae65717344885
I’m thinking this may be the issue because I pieced this together based on past ansible-lemmy changes as the newer version seems to be geared towards 0.18.0 and doesn’t appear to pass into the UI (port 1234) any more.
Any ideas? Thanks in advance!
Apologies - This is a repost. Seems my last question got lost in all the turbulence over the last 4 days but the issue continues here.
Thank you for the help so far! Another user successfully sent me a message so it seems some things are working. I do have federation enabled in settings (see image)
Do I need to specifically list all the instances I want to federate with? That seems counter intuitive as by default I’d like to federate with all instances and just block the ones that give me a headache.
My lemmy.hjson looks like this:
{ database: { password: "NOT REAL PASSWD" } # replace with your domain hostname: discuss.petersanchez.com bind: "127.0.0.1" federation: { enabled: true } # remove this block if you don't require image hosting pictrs: { url: "http://localhost:8080/" } }I don’t even know what other options are available for this file. I can’t seem to find any docs for it. Let me know if something should be added/removed/changed.
DNS seems OK on the system when trying to resolve all the given communities from a server shell. I know ActivityPub isn’t for the faint of heart but in my toying around with it in the past, it was straight forward enough, just different software use different fields for different purposes. So that can create confusion in federation but in this case I’m dealing with Lemmy to Lemmy so I assume it should work heh.
Oh and the 1 community I was able to actually find is on kbin.social and it says subscribe pending:
Thanks again for the help so far!