RX_RECORD_TOO_LONG. This happens regardless of whether I try to download the image using Firefox or cURL and regardless of what internet connection I use. My instance is able to proxy them though, strangely.
I suppose I could try writing my own little download utility using a different SSL library, but I don’t wanna do that right now.
Sounds like a misconfiguration (HTTPS on an HTTP port or some other non-HTTPS protocol).
I’ve seen this before in only one instance, which is when archive.is started blocking Cloudflare’s DNS (because they use DNS to hack together a CDN and Cloudflare doesn’t send the optional data they need), but that would make it intentional. If catbox is sabotaging DNS providers the same way, maybe try another upstream DNS server.
…okay, so it’s not just me that gets an SSL error every time someone hosts an image on catbox.moe, right?
I did it specifically because I didn’t want you to see this meme. It’s not for your eyes.
Works fine here. Could be a broken CDN server, or someone is messing with your internet connection. What’s the error?
RX_RECORD_TOO_LONG. This happens regardless of whether I try to download the image using Firefox or cURL and regardless of what internet connection I use. My instance is able to proxy them though, strangely.
I suppose I could try writing my own little download utility using a different SSL library, but I don’t wanna do that right now.
Sounds like a misconfiguration (HTTPS on an HTTP port or some other non-HTTPS protocol).
I’ve seen this before in only one instance, which is when archive.is started blocking Cloudflare’s DNS (because they use DNS to hack together a CDN and Cloudflare doesn’t send the optional data they need), but that would make it intentional. If catbox is sabotaging DNS providers the same way, maybe try another upstream DNS server.
I changed my DNS to quad9 and that fixed it. Wild.
Must be the same type of misconfiguration/sabotage, then. How annoying.