Vollstaendiger CT-scoped Sollzustand fuer den Reverse-Proxy-LXC: Konten/SSH-Drop-in (reverse_proxy_access), nftables (reverse_proxy_firewall), NPM- und Fail2Ban-Quadlets inkl. Jails/Filter (reverse_proxy_npm, reverse_proxy_fail2ban), LXC-Baseline sowie preflight/audit/bootstrap/ verify-deploy-access/site/verify-production-Playbooks fuer die Inventare agent/bootstrap/production. NPM-Runtime-Daten (DB, Zertifikate, Proxyhosts) bleiben bewusst aussen vor (Restore aus CT-Backup). Verifiziert am 09.11.2026 gegen den Live-Host: preflight.yml (agent) ok=15 failed=0; verify-production.yml (production) ok=27 changed=0 failed=0; site.yml --check changed=0 (konvergent und idempotent). Host-Key-Fingerprint, Hostname, Debian 13.7, 10.0.0.10, 2 vCPU/1024 MB matchen die Inventory-Safeguards. Generated by Mistral Vibe. Co-Authored-By: Mistral Vibe <vibe@mistral.ai>
600 B
600 B
CT 103 – Reverse proxy
Host root for Nginx Proxy Manager and Fail2Ban at 10.0.0.10.
The complete desired state lives in the CT-scoped Ansible project
ansible/ (access accounts, SSH baseline, nftables, the NPM and
Fail2Ban Quadlets and the local Fail2Ban jails/filters). Generated NPM files
must not be edited as the authoritative source; NPM runtime data (database,
keys, certificates, proxy hosts) is restored from the CT backup.