this post was submitted on 07 Jun 2023
2 points (100.0% liked)

Lemmy Support

4719 readers
25 users here now

Support / questions about Lemmy.

Matrix Space: #lemmy-space

founded 5 years ago
MODERATORS
 

Federation on my instance isnt working although I enabled it. I'm getting this error when I try to search for lemmy communitys on other instances

lemmy-lemmy-1 | at src/root_span_builder.rs:16 lemmy-lemmy-1 | 2023-06-07T15:54:10.678358Z ERROR HTTP request{http.method=GET http.scheme="https" http.host=lemmy.ohaa.xyz http.target=/api/v3/ws otel.kind="server" request_id=4cd438eb-f7ae-4299-baff-4b83a011dafe http.status_code=101 otel.status_code="OK"}: lemmy_server::api_routes_websocket: couldnt_find_object: invalid query lemmy-lemmy-1 | 0: lemmy_apub::fetcher::search::search_query_to_object_id lemmy-lemmy-1 | at crates/apub/src/fetcher/search.rs:17 lemmy-lemmy-1 | 1: lemmy_apub::api::resolve_object::perform lemmy-lemmy-1 | with self=ResolveObject { q: "sdfsdf", auth: Some(Sensitive) } lemmy-lemmy-1 | at crates/apub/src/api/resolve_object.rs:21 lemmy-lemmy-1 | 2: lemmy_server::root_span_builder::HTTP request lemmy-lemmy-1 | with http.method=GET http.scheme="https" http.host=lemmy.ohaa.xyz http.target=/api/v3/ws otel.kind="server" request_id=4cd438eb-f7ae-4299-baff-4b83a011dafe http.status_code=101 otel.status_code="OK" lemmy-lemmy-1 | at src/root_span_builder.rs:16
Im using the docker container with default nginx config behind a caddy reverse proxy on another machine. My instance url if that helps: https://lemmy.ohaa.xyz

top 8 comments
sorted by: hot top controversial new old
[–] [email protected] 1 points 2 years ago (1 children)

Does your docker network setup have the lemmy server on an internal network with no external access? The default docker config is setup that way and caused what you're describing for me. Fastest fix is comment out the "internal: true" from the docker compose file, but you may want to consider the security implications of that.

[–] [email protected] 1 points 2 years ago (1 children)
[–] [email protected] 2 points 2 years ago (2 children)

Yeah. Did you down and up the docker and see if the issue is resolved?

[–] [email protected] 1 points 2 years ago (1 children)
[–] [email protected] 1 points 2 years ago

same error after modifying the file and recreating the container

[–] [email protected] 1 points 2 years ago (1 children)

Restarted and recreated the container and the host. still nothing

[–] [email protected] 1 points 2 years ago

Not sure then, sorry :/

[–] [email protected] 1 points 2 years ago

I have the exact same error with the ansible playbook