5 hours ago
The error in the logs is:
Prisma error P1001: Can't reach database server at postgres.railway.internal:5432
The Backend’s DATABASE_URL variable is configured and corresponds to the existing PostgreSQL database in the same project. This PostgreSQL database contains important data from my system, and I DO NOT want it to be recreated, deleted, reset, or replaced.
I only want you to diagnose the cause of the P1001 error and tell me exactly what is preventing the Backend from connecting to PostgreSQL.
Please check the networking configuration, service references, environment variables, and compatibility between the Free plan/Serverless configuration and the PostgreSQL service.
Do not make any destructive changes to the PostgreSQL database. Do not delete, recreate, reset, or replace the database.
1 Replies
5 hours ago
Your Postgres service's latest deployment has failed with a "Free plan deployments must be serverless" error, so the database is not running at all. That is why the backend cannot reach postgres.railway.internal:5432. Serverless is now enabled on the Postgres service's config, but the service still needs a new deployment for that setting to take effect. Open the command palette (Ctrl/Cmd + K), select the Postgres service, and deploy the latest commit to bring the database back online. Your existing data on the attached volume will not be affected by redeploying.
Status changed to Awaiting User Response Railway • about 5 hours ago