Apollo Town - A brand new Lemmy instance
apollo.town

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
}
  • tekeous@beehaw.orgOPEnglish
    1·
    1 year ago

    I think you might be on to something. I looked up myself(@[email protected] 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: "@[email protected]", 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.devEnglish
      1·
      1 year ago

      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@beehaw.orgOPEnglish
        2·
        1 year ago

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

        • pe1uca@lemmy.pe1uca.devEnglish
          1·
          1 year ago

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