Skip to content

Help

Troubleshooting

Tested with:Databasezy API v1 · zb CLI 0.1

Most problems fall into a few groups: the client cannot reach the instance, the instance refuses the login, it is out of connections or resources, or it is paused. Check the instance’s status first, then open the article that matches the error text you see. Every article starts with the most likely cause.

Many errors are just an instance that is not running yet, or not running any more.

shell
zb instances get <instance_id>

The status column shows what the instance is doing now, and a message: line explains a failure. The statuses you will see:

StatusMeaning
requested, provisioningBeing created. Connections fail until it is ready
readyRunning and accepting connections
modifyingA resize, storage grow or upgrade is in progress
restoringA restore is running
paused, archivedCompute is stopped. See Paused and waking instances
suspendedStopped for billing or a quota. See Spending caps and quota errors
failedSomething went wrong. Read the message, then open a ticket if it is not clear

In the portal, open the instance and look at the header and the Timeline tab for recent changes. From the CLI, zb logs <instance_id> -f streams the instance’s events (status changes, backups, migrations). Engine logs are not available through the API yet.

Each engine has its own error messages. See Engine errors for PostgreSQL, MySQL, Valkey and the other engines.

Search the help center or ask the assistant in the portal Help panel. If that does not solve it, open a support ticket from the portal (Help → Open a ticket). Include the instance id, the region, the exact error text, your client or driver version, and the time it happened in UTC. Never paste passwords, connection strings with passwords, API keys or patient data (PHI) into a ticket. See How to get help.