And it always causes issues.

Anyway, I hope the main joke got spotted too.
Let’s Encrypt now does IP certs: https://letsencrypt.org/2026/01/15/6day-and-ip-general-availability

Certbot doesn’t seem to be up to the task yet, but lego works.

But I’ll probably change it to some image host later, because I have no idea what I am doing.

Why does it not work… It embeds when creating the post.

Seems fine too, it’s HTTPS after all, should work.

OK, seems that it’s just the default LemmyUI that doesn’t like it, which is strange for the number of pict-rs requests in access.log.
Also by the number of 429, 5r/s is probably too low. Was. Anyway…
OR, that’s why there is the burst option. Right.

    • Scoopta
      link
      fedilink
      arrow-up
      1
      ·
      2 months ago

      I deliberately don’t want or use a clat, the goal is to avoid IPv4

      • the rizzler@lemmygrad.ml
        link
        fedilink
        arrow-up
        1
        ·
        2 months ago

        i see. does that meaningfully reduce the amount you use nat64? i ask because for me, most things go through dns anyway

        • Scoopta
          link
          fedilink
          arrow-up
          1
          ·
          2 months ago

          No not really, I just don’t like having the address on my interface, ironically it doesn’t break half the stuff that removing 127.0.0.1 does…but I do that too XD. Removing loopback isn’t actually THAT bad but I’ve found more stuff that struggles with that than with not having a clat