Troubleshooting

Prisma cannot reach the database

Check:

1. your current IP is allowlisted,
2. DATABASE_URL uses db.squareexp.com:6432,
3. DIRECT_URL uses db.squareexp.com:5432,
4. both URLs include sslmode=require,
5. the branch database exists and is active.

Prisma cannot create shadow database

Use DIRECT_URL in schema.prisma.

datasource db {
  provider  = "postgresql"
  url       = env("DATABASE_URL")
  directUrl = env("DIRECT_URL")
}

If it still fails, rotate or repair the direct owner role.

PgBouncer cannot connect to server

Usually this means PgBouncer userlist, Postgres role password, database name, or network policy drifted.

Fix path:

1. test DIRECT_URL,
2. verify role exists,
3. refresh PgBouncer config,
4. reload PgBouncer,
5. retry DATABASE_URL.

Network save says failed but table changed

That is control-plane/apply drift. The rule was stored, but the VPS apply step failed. The UI should show a sanitized error and the backend should mark the apply event failed.

Retry after fixing the provisioner or remove the stale rule.

Empty schema returns error

An empty branch should show an empty table state. It should not be treated as a failure.