#Problems after automated migration postgress

12 messages · Page 1 of 1 (latest)

long sage
#

After the automatic migration I cant get my project back online; https://railway.app/project/013f57ee-d1de-40b7-81af-61b809ca2682

Problem 1

NextJS instance build errors

I have a nextjs frontend working with a Strapi api, so no database needed. I suppose the migration-process added some database variables to the NextJS instance (I cant find a backup of the old situation, hopefully you have one). After only keeping the variables I think are needed, the app still doesnt start. This maybe caused by problem 2 but I dont know for sure.

Problem 2

Strapi instance build errors

I think this also has to do with the variables that are edited automatically, but I dont have a backup of the old variables.

Can you please help to get the app back online?

Railway

Railway is an infrastructure platform where you can provision infrastructure, develop with that infrastructure locally, and then deploy to the cloud.

opaque glacierBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

void zealotBOT
#

Project ID: 013f57ee-d1de-40b7-81af-61b809ca2682

long sage
#

The DB is running though, the rest isnt.

zenith escarp
#

This is related to our ongoing in incident, I will update you when we have it resolved and will be around to help if it still isn't working for you: #🚨|incidents message

long sage
#

Ok thanks!

long sage
#

It still isnt working for me.

#

Both still failing

unkempt brook
long sage
unkempt brook
#

@long sage - your strapi build is using node 14, that has reached end of life and is no longer supported on railway, please use at minimum node 18, this can usually be achieved by setting engines.node to 18 in your package.json.

as for your frontend, thats looking more like a code issue, can you successfully run npm run build locally? and would you mind sending me your package.json for that?

long sage
#

Thanks, I upgraded the Node version and it fixed the backend. Thereby the frontend as well. Thanks so much for the help!