Just a very quick, specific, thing that annoyed me yesterday. I have a server running RunTiPi for various self hosted things. To channel some specific services to it I use cloudflare tunnels so as to avoid the usual faff and security implications of opening ports on my router.

Last night I spent a good 30 minutes trying to identify why a route I had made wasn't working.

Turns out, the Cloudflare backend for routes makes a cname record for each subdomain. But this isn't an infallible process, therefore sometimes when deleting/renaming/removing routes this record isn't created and the route doesn't work.

To fix it, just rename the route you're interested in e.g. from links to links2 and then rename it back. Voila, it's created.

Then you have to wait for DNS changes to propagate, but a quick nslookup yoursub.domain 1.1.1.1 to check to see that it's working and not just returning errors - 20 minutes later, you're good to go.

Cloudflare Tunnel not always creating CNAME records - fyi