2 ms·

I'm curious, but how/what is the actual problem there? I can connect over IPv6 just fine, and IPv6 shouldn't make a difference to TLS¹? (¹in this case)

• stagas 1mo ago
  I’m not an expert on networking but that’s the verdict I get when pasting this problem to ChatGPT. We did have this and went away when we activated IPv6. Firefox and depending on your network/OS you might access the site via IPv6, in which case it will fail if it’s not accessible. I still have problem accessing it locally, curl fails, it works when I am in the network, so I don’t know what’s the case here. It works for some and not for others? Super weird.
  • deathanatos 1mo ago
    Well, that sounds hallucinogenic; v6 & TLS should basically not interact. But like, what error does curl give? I'm sort of wondering if it's more cert store weirdness. Curl & Firefox, I think, will use different stores. I think FF uses Mozilla's cert store, always, whereas curl will default to the local machine's store. The site is also using the LE YE1 cert — i.e., it's using an EdDSA cert, which is a bit unusual. It's also serving the root cert itself, which it shouldn't do, but also shouldn't be fatal. (But that also results in a whopping 4 certs sent by the server, which is also quite unusually high, but again, shouldn't be fatal.) But EdDSA is also odd enough I could see it fouling something up, and TLS libraries and path building is source of so many bugs.