update:
it work with the build : FIx display correct requests in requests...

all the other builds, new builds, don't work.

Your site seems to work okay for me now. Are you still having issues with this?

did you read my last message.

I think one of those SSL config changes broke it. your deploy logs look fine (Next.js starts, Prisma connects successfully) which means the app boots but something in those SSL/config changes is causing requests to fail.

i'd check whatever you changed in that auto-config logic - probably something with how you're handling the DATABASE_URL or SSL settings for the postgres connection. the fact that the older build works confirms it's a code change, not a Railway issue.

Hi, my story might help you. I have similar problem in my Django app with Postgres database, I have solved the problem, here the summary:

The error:

App do not respond

502 Bad Gateway

The log:

DETAIL: The database was created using collation version 2.36, but the operating system provides version 2.41.

HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE railway REFRESH COLLATION VERSION, or build PostgreSQL with the right library version.

Operations to perform:

Apply all migrations: <all table listed here>

What I am done to fix:

1. Backup in the local

BACKUP

436 export PGHOST="pghost"

437 export PGPORT="pgport"

438 export PGUSER="pguser"

439 export PGPASSWORD="pgpassword"

440 export PGDATABASE="pgdatabase"

441 export PGSSLMODE="require"

442 pg_dump --no-owner --no-privileges --format=plain > backup.sql

after finish

443 ls

you will get

backup.sql

2. TEST

444 createdb test_restore\npsql test_restore < backup.sql\npsql test_restore -c "\dt"\n

you will get error here

3. ALTER and REINDEX

445 psql -d postgres -c "ALTER DATABASE template1 REFRESH COLLATION VERSION;"\n

446 psql -d postgres -c "ALTER DATABASE postgres REFRESH COLLATION VERSION;"\n

447 psql -d postgres -c "ALTER DATABASE railway REFRESH COLLATION VERSION;"\n

448 psql -d postgres -c "REINDEX DATABASE railway;"\n

449 psql -d railway -c "REINDEX DATABASE railway;"\n

450 psql -d postgres -c "ALTER DATABASE postgres REFRESH COLLATION VERSION;"\n

451 psql -d postgres -c "ALTER DATABASE railway REFRESH COLLATION VERSION;"\n

452 psql -d railway -c "REINDEX DATABASE railway;"\n

453 psql -d railway -c "SELECT current_database();"\n

454 psql -d railway -c "VACUUM (ANALYZE);"\n

455 psql -d railway -c "SELECT pg_database_size(current_database());"\n

Hope this help you.

still not working.

try clear cache and take it out after deployment if its working

NIXPACKS_NO_CACHE=1

add this to env variables

when you say it doesn't work, what is not working? are there any error logs?

could you solve it?