Knowledge base
How Vigavo works, what each error means and how to fix it.
All articles
- Acknowledge, snooze or accept a finding
- Alert channels (email, Telegram, Slack, webhook)
- Backup failed (BK-* codes)
- Bring your own bucket (BYO storage)
- Connect PostgreSQL or MySQL for backups
- Connect Supabase for backups (read-only role)
- Connection test failed (CN-* codes)
- Deploy hook (scan after each deploy)
- DNS and email protection
- Download a snapshot
- Exposed files and folders
- Firebase security rules
- Free vs paid
- HTTPS and certificates
- Install the WordPress plugin
- Lifetime codes and stacking
- Managed by your platform: why can't I fix it?
- Monitoring schedules per plan
- Plans and limits (and monthly vs yearly)
- Prove a site is yours (verified domains)
- Reading your score and grade
- Refunds, invoices and price changes
- Restore a database
- Restore a table
- Restore drills
- Restore failed (RS-* codes)
- Scan failed (SC-* codes)
- Scan safety and opting out
- Secrets in your website's code
- Security headers and cookies
- Something broke or data is missing: what to do first
- Storage caps and retention
- Supabase Row Level Security and Storage
- Supported platforms and what Vigavo can do on each
- The 15 most common findings and what to do
- Using a fix prompt in Claude Code, Cursor, Lovable or Bolt
- Verify failed (BK-VERIFY)
- Verifying a fix (rescan)
- What is and is not backed up
- What Vigavo does
- Where your data lives and who can see it
- WordPress checks
- Your first scan