Hello!
I recently turned up a Lemmy server but it appears there’s an issue communicating with other servers. Curling activity json is working for local users, communities, and posts. Does anyone see anything off? Trying to see a user or community apart of another server results in a 404 and vise versa.

https://Lemmy.kutara.io

For example viewing this community from my server results in a 404

https://lemmy.kutara.io/c/[email protected]

Viewing my account from this server results in 404 as well

https://sh.itjust.works/u/[email protected]

EDIT: Thanks for all the help! My solution was here https://sh.itjust.works/comment/113460

  • ActuallyRuben@actuallyruben.nlEnglish
    3·
    2 years ago

    For a community or user to show up, you need to first search for it. Try entering @anthr76@lemmy.kutara.io on https://sh.itjust.works/search, and !lemmy_support@lemmy.ml on https://lemmy.kutara.io/search (while logged in on those respective instances). After doing that those links shouldn’t 404 anymore.

    I was able to look up your user from my personal instance this way: https://actuallyruben.nl/u/[email protected]

    • BarbarianEnglish
      2·
      2 years ago

      Was half-way through typing exactly that and you beat me to it :)

      • ActuallyRuben@actuallyruben.nlEnglish
        2·
        2 years ago

        Heh, it’s kinda unfortunate this explanation is needed anyway, I do hope they’ll streamline this process somehow in the future.

        • BarbarianEnglish
          1·
          2 years ago

          Yeah, visiting that URL should cause a loading animation while it does the search in the background, and then show you the result. Quite a big and complex change to make, but it would improve the user experience tremendously.

          • ActuallyRuben@actuallyruben.nlEnglish
            2·
            2 years ago

            That would be a start, but the fact that you have to search at all for it to show up is kinda unintuitive. Honestly I’m not entirely sure what would be a better method, though.

  • Madiator2011@lm.madiator.cloudEnglish
    1·
    2 years ago

    If you use Nginx proxy manager this is what fixed my federation issues:

    location / {
      # The default ports:
      # lemmy_ui_port: 1235(not used here)
      # lemmy_port: 8536
	  # The cooler port:
	  # lemmy_ui_port: 1236

      set $proxpass "http://172.16.7.20:1236";
      if ($http_accept ~ "^application/.*$") {
        set $proxpass "http://172.16.7.20:8536";
      }
      if ($request_method = POST) {
        set $proxpass "http://172.16.7.20:8536";
      }
      proxy_pass $proxpass;

      rewrite ^(.+)/+$ $1 permanent;

      # Send actual client IP upstream
      proxy_set_header X-Real-IP $remote_addr;
      proxy_set_header Host $host;
      proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    }
  • oneOPEnglish
    1·
    2 years ago

    deleted by creator