Connection test failed (CN-* codes)

Before Vigavo saves a database connection it connects once, runs a few read-only test queries and checks whether the user can write. If that fails you see one of these codes.

What each code means

• CN-URL: the connection string could not be read. It must look like postgresql://user:password@host:5432/database (or mysql://… for MySQL). Multi-host strings are not supported.
• CN-DNS: the host name does not resolve. Check for typos and copy the host again from your provider.
• CN-REFUSED: the host is a private, loopback or reserved address (for example localhost or 10.x.x.x). Vigavo only connects to public addresses. Use the public or pooler host your provider shows.
• CN-AUTH: the database refused the user name or password. Create the read-only user again with the SQL shown in the wizard and paste the new password.
• CN-NET: the database could not be reached in time. Common causes: the wrong port, a firewall or IP allow-list that blocks us, or a database that is paused.
• CN-QUERY: we connected, but a test query failed. Usually the user has no USAGE on a schema; run the GRANT lines from the wizard again.
• CN-WRITE: the connection works, but the user can write (or is a superuser). Backups still run, but we recommend the read-only user from the wizard.

Supabase

Use the pooler connection string from the Supabase dashboard (Project settings, Database). The SQL in the wizard creates vigavo_ro with read access to the public, auth and storage schemas. For new Supabase projects on PostgreSQL 17 see Backup failed.

After a fix

Run the test again from the Backups tab. The password is never shown back to you and never appears in error messages. If it still fails, send a ticket with the code (never the password).