#New issues deploying on Railway

9 messages · Page 1 of 1 (latest)

violet bridge
#

I've encountered a new error when deploying payload to Railway.
Using the same code base with just some later packages, all deploying and building correctly but when I try to access admin panel getting a white screen and the following error in the console

Any ideas how I might start debugging this.

No errors in build or deploy logs.

proper kelpBOT
violet bridge
#

├── @aws-sdk/client-s3@3.567.0
├── @aws-sdk/lib-storage@3.567.0
├── @payloadcms/bundler-webpack@1.0.6
├── @payloadcms/db-postgres@0.8.2
├── @payloadcms/plugin-cloud-storage@1.1.2
├── @payloadcms/plugin-cloud@3.0.0
├── @payloadcms/richtext-lexical@0.8.0
├── @payloadcms/richtext-slate@1.5.1
├── @types/express@4.17.21
├── copyfiles@2.4.1
├── cross-env@7.0.3
├── dotenv@8.6.0
├── express@4.19.2
├── nodemon@2.0.22
├── payload@2.14.2
├── ts-node@9.1.1
└── typescript@4.9.5

#

I can't see any settings between a project on railway that is working correctly and this project except a few packages being later version - going to list the differences here and perhaps roll a couple back

#

Looks lile the db-postgres and payload versions are different. I'm going to roll them back see if I can get it to load the admin panel in production - to clarify no errors on build, no errors locally in dev.

violet bridge
#

Rolling back these packages has it loading correctly now:

"@payloadcms/db-postgres": "0.7.0",
"payload": "2.11.2"

I'll try and go back and work out which one is the problem this weekend

#

/solved

wispy crown
#

Good morning

#

This is all set?