this post was submitted on 14 Jun 2023
3 points (100.0% liked)

Lemmy Support

4652 readers
1 users here now

Support / questions about Lemmy.

Matrix Space: #lemmy-space

founded 5 years ago
MODERATORS
 

I'm trying to set up a personal Lemmy instance, and I haven't been able to connect to any remote instances.

The JSON test at https://join-lemmy.org/docs/en/administration/troubleshooting.html#other-instances-cant-fetch-local-objects-community-post-etc returns valid JSON for my instance, and when I attempt to access a community on my instance from another, it does show my community exists, but when I try to subscribe it gets stuck on "subscribe pending" with a similar error in my instance's logs.

Federation is enabled on my instance, and I have tried first searching for the community I want.

The error appears to be related to DNS resolution, and indeed I am unable to connect to the Internet at all in the lemmy-lemmy-1 container.

 WARN Error encountered while processing the incoming HTTP request: lemmy_server::root_span_builder: couldnt_find_community: Request error: error sending request for url (https://lemmy.ml/.well-known/webfinger?resource=acct:lemmy_support@lemmy.ml): error trying to connect: dns error: failed to lookup address information: Try again
2023-06-14 13:13:41    0: lemmy_apub::fetcher::resolve_actor_identifier
2023-06-14 13:13:41              at crates/apub/src/fetcher/mod.rs:16
2023-06-14 13:13:41    1: lemmy_apub::api::read_community::perform
2023-06-14 13:13:41            with self=GetCommunity { id: None, name: Some("lemmy_support@lemmy.ml"), auth: Some(Sensitive) }
2023-06-14 13:13:41              at crates/apub/src/api/read_community.rs:30
2023-06-14 13:13:41    2: lemmy_server::root_span_builder::HTTP request
2023-06-14 13:13:41            with http.method=GET http.scheme="http" http.host=lemmy.edgeburnmedia.com http.target=/api/v3/community otel.kind="server" request_id=74953f46-d6a8-41f9-8c4e-6ac51676bb83 http.status_code=400 otel.status_code="OK"
2023-06-14 13:13:41              at src/root_span_builder.rs:16
2023-06-14 13:13:41 LemmyError { message: Some("couldnt_find_community"), inner: Request error: error sending request for url (https://lemmy.ml/.well-known/webfinger?resource=acct:lemmy_support@lemmy.ml): error trying to connect: dns error: failed to lookup address information: Try again
2023-06-14 13:13:41 
2023-06-14 13:13:41 Caused by:
2023-06-14 13:13:41     0: error sending request for url (https://lemmy.ml/.well-known/webfinger?resource=acct:lemmy_support@lemmy.ml): error trying to connect: dns error: failed to lookup address information: Try again
2023-06-14 13:13:41     1: error trying to connect: dns error: failed to lookup address information: Try again
2023-06-14 13:13:41     2: dns error: failed to lookup address information: Try again
2023-06-14 13:13:41     3: failed to lookup address information: Try again, context: "SpanTrace" }
you are viewing a single comment's thread
view the rest of the comments
[–] nii236@lemmy.jtmn.dev 2 points 1 year ago (5 children)

Have you tried a community from another instance? Lemmy.ml has been getting hammered by new traffic so is down a lot

[–] Edgeburn02@sh.itjust.works 1 points 1 year ago (1 children)

I’ve tried a number of instances and I get the same error from of all of them

[–] nii236@lemmy.jtmn.dev 0 points 1 year ago (1 children)

Yeah your container needs access to a bridged or host network. Not sure how your docker daemon is setup, but its missing that

[–] Edgeburn02@sh.itjust.works 0 points 1 year ago* (last edited 1 year ago) (1 children)

~~I'm honestly not all that familiar with Docker, are there any specific resources you could point me towards for how to do this? My instance is being hosted on Windows Server (I know, bad choice, but I'm using this VPS for now until I can change to a Linux based one)~~ I've switched my VPS to a Linux based host and now the docker compose doesn't work at all anymore so who knows

[–] nii236@lemmy.jtmn.dev 0 points 1 year ago (1 children)
[–] Edgeburn02@sh.itjust.works 1 points 1 year ago

I've been having this issue, and I've been thus far unsuccessful in fixing it.

load more comments (3 replies)