Since I moved my server to ipv6 only federation broke. I’m guessing this server is acessible trough the cloudflare proxy, but the underlying server is unable to connect to mine

Edit:

This is what I get in the logs:

2023-09-27T19:17:23.955421Z DEBUG activitypub_federation::activity_queue: Activity https://lemmy.fbmac.net/activities/undo/506ed9a4-bfee-472f-8249-f802639eec8d was rejected by https://lemmy.world/inbox, aborting: Request error: error sending request for url (https://lemmy.fbmac.net/u/fbmac): error trying to connect: tcp connect error: Address not available (os error 99)

I think it kind of confirms, lemmy.world is unable to contact mine back.

What servers are really IPV6, so I can actually federate with something?

  • @dindrestoA
    link
    English
    31 year ago

    It’s a real shame, I started out with IPv6-only on my self hosted instance but then had to add a public IPv4 as I wasn’t able to federate with any of the big instances.

    • @fbmac2@lemmy.worldOP
      link
      fedilink
      English
      41 year ago

      I’ll let mine this way, someone has to be the first

      can you try to browse anything from lemmy.fbmac.net from your instance to see if it works? I didn’t find any other instance that it’s able to federate yet

  • @Scoopta@programming.dev
    link
    fedilink
    English
    31 year ago

    I’ve been contemplating spinning up lemmy in my infra which is also v6 only…good to know about this gotcha…it blows that this community is on an instance that won’t federate over v6 though ://

    • @fbmac2@lemmy.worldOP
      link
      fedilink
      English
      21 year ago

      All lemmy instances that I looked at have this problem. I gave up and used cloudflare for a while, and now I have an IPV4 machine that use haproxy and an ssh tunnel to forward everything to my server. The AAAA record points directly to my server

      I’m not happy with this setup, but my instance wasn’t very useful without connecting to anything else