Your one-stop-cake-shop for everything Freshly Baked has to offer

fix(pm/acme): resolve DNS using cloudflare #120

closed opened by a.starrysky.fyi targeting main from private/minion/push-oqywmpqruopz

We run Tailscale, which sometimes has internal routes to things. These override all DNS address entries for specified domains, which breaks verifying ACME TXT records, which prevents us fetching certificates.

Resolving ACME using Cloudflare avoids the issue...

Labels

None yet.

requested-reviewers

None yet.

approved

None yet.

tested-working

None yet.

rejected

None yet.

assignee

None yet.

Participants 1
AT URI
at://did:plc:uuyqs6y3pwtbteet4swt5i5y/sh.tangled.repo.pull/3mavdhtp6v422
+8
Diff #3
+4
packetmix/systems/teal/acme.nix
··· 9 9 email = "acme@freshlybakedca.ke"; 10 10 dnsProvider = "cloudflare"; 11 11 environmentFile = "/secrets/acme/environmentFile"; 12 + extraLegoFlags = [ 13 + "--dns.resolvers" 14 + "1.1.1.1" 15 + ]; 12 16 }; 13 17 }; 14 18
+4
packetmix/systems/umber/acme.nix
··· 9 9 email = "acme@starrysky.fyi"; 10 10 dnsProvider = "cloudflare"; 11 11 environmentFile = "/secrets/acme/environmentFile"; 12 + extraLegoFlags = [ 13 + "--dns.resolvers" 14 + "1.1.1.1" 15 + ]; 12 16 }; 13 17 }; 14 18

History

4 rounds 1 comment
sign up or login to add to the discussion
1 commit
expand
fix(pm/acme): resolve DNS using cloudflare
expand 1 comment

manually merged due to tangled error

closed without merging
1 commit
expand
fix(pm/acme): resolve DNS using cloudflare
expand 0 comments
1 commit
expand
fix(pm/acme): resolve DNS using cloudflare
expand 0 comments
1 commit
expand
fix(pm/acme): resolve DNS using cloudflare
expand 0 comments