Skip to content

Help

Engine errors

Tested with:Databasezy API v1 · zb CLI 0.1

All 18 engines in the Databasezy catalogue are available today. Some run on paid plans only. Each page below lists the error messages people hit most often with one engine family, what causes each one, and how to fix it. Search for the exact error text, or open the page for your engine.

EnginePage
PostgreSQLPostgreSQL errors
MySQL, MariaDBMySQL and MariaDB errors
Valkey, Redis (compat)Valkey and Redis errors
MongoDB (Percona Server), FerretDBMongoDB and FerretDB errors
ClickHouseClickHouse errors
libSQL / SQLite, DuckDBlibSQL and DuckDB errors
Qdrant, Weaviate, MeilisearchQdrant, Weaviate and Meilisearch errors
InfluxDB 3, QuestDB, TimescaleDBInfluxDB, QuestDB and TimescaleDB errors
CouchDB, TypeDBCouchDB and TypeDB errors

Is the error from the engine or from Databasezy?

Section titled “Is the error from the engine or from Databasezy?”

Every connection passes through the Databasezy gateway. The gateway checks TLS, the allow-list, pause state and connection limits before the database sees anything. When it refuses a connection, it answers in your engine’s own protocol, so the error looks like a database error. These messages come from the gateway:

MessageMeaning
too many connections for this instanceThe size’s connection limit is reached
connection rate limit exceeded; slow downMore than 50 new connections in one second
paused: the instance is paused by its owner; resume it in the portal or with `zb instances resume`Someone in your organization paused the instance. Connections never wake it; resume it
paused: the instance was paused by Databasezy support; contact support to resume itSupport paused the instance. Only support can resume it
the instance is waking up; retry in a few secondsA paused instance did not wake within the 30-second hold
the instance is moving; retry in a few secondsThe instance is being moved. Retry
suspended: the instance is suspended (...)Billing suspended the instance, or it was archived
quota_exceeded: the instance is suspended (...)A plan quota ran out
instance unavailable; retry in a few secondsThe gateway could not reach the database

HTTP engines get the same reasons as JSON, with an HTTP status: 429 for connection limits, 502 when the database is unreachable, and 503 for the rest.

Some failures have no message at all: the gateway closes the connection during the TLS handshake. That happens when:

  • your address is not on the allow-list
  • the client did not use TLS
  • the client sent no TLS server name, for example because you connected by IP address
  • your address is temporarily blocked after repeated failed logins (by default, 10 within a minute block it for 10 minutes)

Anything else, such as wrong passwords, SQL errors, permission errors and memory limits, comes from the engine itself.

For each engine’s ports, versions, backups and limits, see Engines and the engine catalogue.

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) and include:

  • the instance id, engine and region
  • the exact error text
  • your client or driver and its version
  • the time of the failure in UTC

Never paste passwords, connection strings with passwords, API keys or patient data (PHI) into a ticket. See How to get help.