seriously, wtf @cloudflare

https://github.com/ddclient/ddclient/issues/820

this broke my vpn because the dns was set to 1.0.1.1 instead of the actual ip.

(real ip obfuscated but you can clearly see it's different to 1.0.1.1)

thankfully there is a workaround for now

#ddns #ddclient #cloudflaresucks #networking #vpn

If you're running an #ActivityPub server, you might think carefully about how you use something like Cloudflare. I just spent 30 minutes troubleshooting why my AP server was getting a 403 when trying to pull up someone's webfinger, but I could issue the same exact command via curl (same UA, headers, HTTP version, IP address, etc.) and it worked fine.

I've finally decided that it's just Cloudflare being a jerk. AP is inherently pretty noisy, but I was making things worse by looking up the webfinger too often. So the server would get hit with 6 requests in quick succession and it seems to be triggering something with Cloudflare. I reduced that to 3 by looking up the webfinger locally, and I can get further. But I still can't pull up this particular full profile (e.g., requesting followers, following, outbox, in quick succession triggers the 403).

This seems to be an uncommon configuration (I have 64,131 Actors currently in my database), but it's annoying. Plus, #CloudflareSucks. They've always sucked.

Use #Fastly if you need a #CDN. Or do it yourself with #Varnish if you just need caching.