Test the connection
Verify Backup can reach your database and authenticate, before scheduling anything.
After saving credentials, test the connection. The test runs a real auth-aware probe – it opens a connection, authenticates with the stored credentials using the same driver Backup uses for real backups (the official PostgreSQL and MongoDB drivers), runs a trivial server query, then exits without taking any backup.
Run a test
- Open the data source in app.norcube.com → Backup.
- Click Test connection.
- Wait a few seconds. The result appears as a status badge.
The dashboard automatically runs this test for you after you save credentials, so a green badge usually appears without you clicking anything. Re-running on demand is useful after rotating credentials or changing your firewall.
Result codes
| Result | Meaning | What to do |
|---|---|---|
| Success | Connected, authenticated, and queried the server. Latency shown in ms. | Move on to attaching a policy. |
| Auth failed | Reached the database, but credentials were rejected. | Double-check user / password. For Postgres, also check pg_hba.conf allows the role from the connecting IP. |
| Timeout | Couldn't open a TCP connection. | Verify your firewall allows 18.196.207.101. Verify the host / port. See Network access. |
| TLS error | Reached the database, but TLS negotiation failed. | Check your TLS configuration. Backup honours sslmode=require (Postgres) and tls=true (Mongo) in the URI. |
| Unreachable | DNS lookup failed or the host wasn't routable. | Check the host name resolves publicly. |
| Server error | Connected and authenticated, but the verification query failed (usually a permissions issue on the role). | Check the role's permissions. See Manage credentials. |
What the test does and doesn't do
It does:
- Open a TCP connection to your host and port.
- Negotiate TLS if your URI requires it.
- Authenticate as the configured user using the official Postgres / Mongo driver.
- Run a trivial server query.
- Report latency.
It doesn't:
- Take a backup.
- Run
pg_dump --schema-onlyor any other test dump. - Check that the role can read every table you'd want backed up.
The first real scheduled backup will fail if the role's grants are insufficient – the test catches the most common failures, not all of them.
Common fixes
- Auth failed against Postgres – check
pg_hba.confallowshost all <role> 18.196.207.101/32 md5(orscram-sha-256). - Timeout from AWS RDS – the security-group inbound rule needs
18.196.207.101/32on the database port. - TLS error on a self-signed cert – Backup won't trust unknown CAs today. Use a publicly-trusted cert (Let's Encrypt etc.) on your database, or contact us.