Database Stopped

database-stopped · 409

Someone stopped the database in this environment, so the API opened no tunnel.

service and environment name the database and the environment it was asked in. --wake wakes a database that is asleep, never one that was stopped. The CLI exits with code 5.

Besides the members every error carries, this type adds service and environment.

Common causes

  • A member stopped the database from the console or the API.
  • --wake was given, but the database was stopped, not asleep.

How to fix the call

  • Ask the user before starting it: it was stopped on purpose.
  • To start it, send POST /v1/services/<id>/start?environmentId=<environment>, then run the same command again; without environmentId, the call starts production.

Example response

json
{
  "type": "database-stopped",
  "title": "Database Stopped",
  "detail": "orders-db is stopped in staging.",
  "service": "orders-db",
  "environment": "staging",
  "requestId": "req-1785231000000-4f7b2c9ae",
  "timestamp": "2026-07-28T09:30:00.000Z",
  "path": "/v1/services/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/tunnels",
  "method": "POST",
  "instance": "POST /v1/services/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/tunnels",
  "status": 409,
  "docs": "https://ghaym.me/docs/errors/database-stopped"
}