Article 13 flashbacks: this is about who controls the infrastructure, who holds the keys.
Claim: manual DNS-01 for wildcard is viable monthly on shared hosting. I do it. Skeptics demanded proof; I deliver.
My setup:
- Registrar: RackNerd (has API, no official plugin)
- Host: Time4VPS shared cPanel
- Goal: *.example.com cert
- Problem: no shell, no certbot, no DNS provider integration
The cron hack:
#!/bin/bash
# Runs on $5/mo HostHatch VPS, not the shared host
# Calls RackNerd API for TXT record, polls propagation, tells cPanel to install
DRIFT_KEY="dp_xxxxxxxx"
DOMAIN="he.net"
CPANEL_USER="net Neutral"
# Step 1: Request cert, get TXT from LE staging
# Step 2: RackNerd API POST /domains/$DOMAIN/records
# Step 3: dig +short TXT _acme-challenge.$DOMAIN until match
# Step 4: acme.sh --renew with live CA
# Step 5: cPanel UAPI SSL::install_ssl cert=$CERT key=$KEY cabundle=$CHAINFull script: 87 lines. Runs every 35 days. Zero manual steps since March 2024.
Time4VPS's TOS updated October 18, 2024. New clause: "automated certificate installation via third-party tools must use officially supported methods." They didn't email existing customers. GDPR Article 5(1)(a) lawful processing question: was this a material change requiring affirmative consent?
Fight me.