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
..
deploy_vaultwarden_playbook.yml	vaultwarden: sign-ups off by default, and publish on loopback only	2026-10-19 22:10:23 +02:00
disable_vaultwarden_sign_ups_playbook.yml	ansible: delete the duplicated vars files, move globals to group_vars/all	2026-09-13 20:58:46 +02:00
setup_backup_vaultwarden.yml	backups: monitor both the dump and the pull, per source	2026-09-14 09:22:12 +02:00
vaultwarden_vars.yml	vaultwarden: sign-ups off by default, and publish on loopback only	2026-10-19 22:10:23 +02:00