personal_infra/ansible
counterweight 751277f0c2
vaultwarden: sign-ups off by default, and publish on loopback only
SIGNUPS_ALLOWED was hardcoded 'true' in the compose file and turned off by a
separate manual playbook, so every routine run of the deploy - site.yml
included - silently re-opened registration. It is now
vaultwarden_signups_allowed, default false.

The port was published as a bare "8222:80". Docker writes its own iptables
rules ahead of UFW, so Vaultwarden answered plain HTTP on the public
interface, bypassing Caddy and TLS. Now 127.0.0.1:8222; verified closed from
outside.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-10-19 22:10:23 +02:00
..
group_vars ntfy-emergency-app: remove it 2026-10-19 22:10:22 +02:00
host_vars rebuild: fold monitoring into spacey and prd-arbret into vipy 2026-10-19 22:10:22 +02:00
infra ntfy-emergency-app: remove it 2026-10-19 22:10:22 +02:00
playbooks jar-lid-archive: a staging deployment on its own box 2026-10-03 23:56:30 +02:00
roles monero: find the chain disk by its label, and a blank one by Proxmox slot 2026-10-17 17:30:57 +02:00
services vaultwarden: sign-ups off by default, and publish on loopback only 2026-10-19 22:10:23 +02:00
ansible.cfg now using password 2026-09-11 17:59:41 +02:00
inventory.ini rebuild: fold monitoring into spacey and prd-arbret into vipy 2026-10-19 22:10:22 +02:00
requirements.yml uptime-kuma: annotate config and drop the unused collection 2026-09-11 22:43:56 +02:00
site.yml ntfy-emergency-app: remove it 2026-10-19 22:10:22 +02:00