Lemmy Support

157 readers

3 users here now

Support / questions about Lemmy.

Matrix Space: #lemmy-space

founded 5 years ago

MODERATORS

dessalines@lemmy.ml

Help with federation on my new instance (apollo.town)

submitted 1 year ago by tekeous to c/lemmy_support@lemmy.ml

22 comments fedilink hide all child comments

G'day, I just got Lemmy going on my site https://apollo.town and it doesn't appear to be federating. I ran through the Lemmy troubleshooting docs and I can return valid JSON from the site, but I can't look up anything on lemmy.ml from my site - although I can look up my site from lemmy.ml.

Caddy is my reverse proxy with the world's simplest config:

root@apollotown:~/lemmy# cat Caddyfile 
# apollo.town Lemmy instance
apollo.town {
	reverse_proxy :4040
}

you are viewing a single comment's thread
view the rest of the comments

[–] lodion@aussie.zone 1 points 1 year ago (18 children)

Sorry I have no idea. I've just never seen an instance "linked" to itself. Something is definitely wrong. Might be easier to blow away the database and start again.

[–] tekeous 1 points 1 year ago (14 children)

Blew away the database and it's still there. Removed all references to apollo.town in the docker-compose, lemmy.hjson, and nginx, other than in the lemmy.json where it SPECIFICALLY says to put your domain name. I'll change that anyway to try it

[–] pe1uca@lemmy.pe1uca.dev 1 points 1 year ago (4 children)

Check the logs, if you see something about http error for lemmy.ml then the issue is the internal network.
Add a 3rd network just like the one for the proxy and add it to the lemmy container.
What happened to me was caused by this, the lemmy container couldn't connect to the internet so it wasn't able to find the other instances.

[–] tekeous 1 points 1 year ago* (last edited 1 year ago) (1 children)

I think you might be on to something. I looked up myself(@tekeous@beehaw.org from apollo.town and got the following:

2023-06-09T04:19:01.663684Z ERROR HTTP request{http.method=GET http.scheme="https" http.host=apollo.town http.target=/api/v3/ws otel.kind="server" request_id=a0092113-8277-47a7-9e73-d9bedd908228 http.status_code=101 otel.status_code="OK"}: lemmy_server::api_routes_websocket: couldnt_find_object: Request error: error sending request for url (https://beehaw.org/.well-known/webfinger?resource=acct:tekeous@beehaw.org): operation timed out
   0: lemmy_apub::fetcher::search::search_query_to_object_id
             at crates/apub/src/fetcher/search.rs:17
   1: lemmy_apub::api::resolve_object::perform
           with self=ResolveObject { q: "@tekeous@beehaw.org", auth: Some(Sensitive) }
             at crates/apub/src/api/resolve_object.rs:21
   2: lemmy_server::root_span_builder::HTTP request
           with http.method=GET http.scheme="https" http.host=apollo.town http.target=/api/v3/ws otel.kind="server" request_id=a0092113-8277-47a7-9e73-d9bedd908228 http.status_code=101 otel.status_code="OK"
             at src/root_span_builder.rs:16

I'm not too familiar with docker networks - how would I add a third one?

[–] pe1uca@lemmy.pe1uca.dev 1 points 1 year ago* (last edited 1 year ago) (1 children)

So you want to have this:

networks:
  # only ports facing any connection from outside
  lemmyexternalproxy:
  lemmybridge:
  # communication between lemmy services
  lemmyinternal:
    driver: bridge
    internal: true

And in the container this.

lemmy:
    image: dessalines/lemmy:0.17.3
    hostname: lemmy
    networks:
      - lemmyinternal
      - lemmybridge
    restart: always

(leave the rest as is, you can name the new network however you want)

[–] tekeous 2 points 1 year ago (1 children)

You're a bloody genius, thank you, that appears to have solved the problem.

[–] pe1uca@lemmy.pe1uca.dev 1 points 1 year ago

Nice! This confirms it, I'll check tomorrow to share this in the repo to update the documentation.

load more comments (2 replies)

load more comments (11 replies)

load more comments (14 replies)