nix-config/hosts
William 58fec03579 Switch ACME to DNS-01 challenge with auto-configured certificates
Changed certificate generation from HTTP-01 to DNS-01 challenge to support
services behind Tailscale/CGNAT IPs. HTTP-01 challenges fail because Let's
Encrypt cannot reach private Tailscale IPs (100.x.x.x) that Cloudflare DNS
points to.

Changes:
- Pre-configure certificates in security.acme.certs using DNS-01 via Cloudflare
- Auto-generate certificate configs from shared/services.nix
  - Alexandria: filters services with host == "alexandria"
  - Trantor: filters services with host == "trantor"
- Updated mkNginxVHosts to use useACMEHost instead of enableACME
- Each domain gets its own certificate configured with DNS-01 challenge

This ensures all services get valid Let's Encrypt certificates even when
accessible only through Tailscale or private networks.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-08 22:53:18 -03:00
..
alexandria Switch ACME to DNS-01 challenge with auto-configured certificates 2025-11-08 22:53:18 -03:00
io fix disko usage for io 2025-11-06 19:59:58 -03:00
modules Remove split DNS module and per-service entries 2025-11-08 21:35:33 -03:00
rotterdam now using flake-parts; refactored nixosConfigurations; using hm standalone 2025-10-14 19:28:30 -03:00
trantor Switch ACME to DNS-01 challenge with auto-configured certificates 2025-11-08 22:53:18 -03:00