Cloudflare
- How I made shipping a side project boring
I have projects on my local machine that nobody else has seen. Not because the ideas were bad, but because getting from localhost to a real URL felt like too much work. Setting up a server takes time. So does DNS, SSL, and deployment scripts. By the time it’s all done, the motivation is usually gone.
- Traefik + Cloudflare: Fix 526 SSL Error by Switching to DNS Challenge
Traefik uses HTTP-01 ACME challenge by default. The way it works is: Let’s Encrypt sends a request to http://yourdomain/.well-known/acme-challenge/<token> and checks that Traefik responds with the right token. If it does, cert issued. The problem is Cloudflare. When the orange cloud proxy is on, Let’s Encrypt’s request hits Cloudflare’s servers, not your origin. Traefik placed the challenge token on the origin. Cloudflare has no idea it’s there. It returns a 404. Let’s Encrypt fails the validation. No cert.
- Cloudflare Pages /opt/build/bin/build: line 39: zola: command not found
While deploying a test Zola site to Cloudflare Pages I recieved the following error in the build logs: /opt/build/bin/build: line 39: zola: command not found The error is because in order to use Zola with Cloudflare Pages you need to specify the version of Zola that you are using in a Production Environment Variable like so: