Hardening checklist
- Serve everything over HTTPS (Reverse proxy and TLS)
- Set
server.frontend_originto your exact web origin. Never use*in production - Back up the master password and
data/separately and test a restore - Set
registration.modetoinvite_onlyorclosedonce your community has joined - Keep
server.dev = false, which hides the Swagger UI and extra logging - Prefer
COVE_MASTER_PASSWORDor a secrets manager over a world-readableconfig.toml - Run the server as an unprivileged user with the data directory owned by that user
- Firewall: expose only 443 (or your proxy port) plus the UDP call ports you need
- Leave
rate_limitenabled; lowerauth_rpsif you are attacked - Pin container image tags and upgrade promptly when security fixes ship
- Limit who is an admin; the owner account should be yours
- Review the audit log in the admin panel occasionally