Our production Next.js app (dashboard, domain app.humanbase.ai) is currently unable to connect to the Railway Postgres database through the configured DATABASE_URL. This causes authentication to break (NextAuth can’t read sessions) and the app returns 500/503 errors.

Impact:

• Users cannot log in (NextAuth adapter_error_getSessionAndUser / SESSION_ERROR).

• /api/auth/check-email returns 500.

• GET https://app.humanbase.ai/api/health returns 503 with database check failing.

Error details (from app logs):

• Prisma error: P1001

• Message: Can't reach database server at ballast.proxy.rlwy.net:59232

• Failing call: prisma.session.findUnique() (NextAuth adapter getSessionAndUser)

Observed behavior:

• Postgres service shows as “Active” and logs show normal checkpoints.

• However, the app runtime cannot reach the proxy host/port (ballast.proxy.rlwy.net:59232), suggesting a proxy/endpoint connectivity issue or the app DATABASE_URL is stale/outdated.

Request:

Please confirm whether the Postgres proxy endpoint ballast.proxy.rlwy.net:59232 is healthy and still valid, whether there was any recent endpoint/port rotation, and what the recommended stable connection string is (preferably an internal/private URL between services). Also confirm if there is any network/SSH/proxy incident affecting database connectivity from services in production.