R
Railway•11mo ago
Pabs3

Paused services due to unpaid invoice are crashing after making payment and redeploying

Hello, my services we paused and removed due to an unpaid invoice. I paid the invoice but not when I redeploy the latest successful deployment it keeps crashing and won't successfully deploy. Not sure what to do at this point. Also wondering if I've lost all my data due to this?
62 Replies
Percy
Percy•11mo ago
Project ID: 4b4b518f-cb21-416d-a748-340536d3017e
Fragly
Fragly•11mo ago
Any error messages?
Pabs3
Pabs3OP•11mo ago
Project Id: 4b4b518f-cb21-416d-a748-340536d3017e
Pabs3
Pabs3OP•11mo ago
this is the only error I am getting
No description
Fragly
Fragly•11mo ago
mind sending full logs using this: https://bookmarklets.up.railway.app/log-downloader/
Fragly
Fragly•11mo ago
that is a very indecisive and yet undescriptive error ngl
Pabs3
Pabs3OP•11mo ago
Hence my confusion. This was working fine before my mess up of not paying. Running the same branch locally starts up the server with no errors. Also does this mean I lost all my data?
Fragly
Fragly•11mo ago
I'm pretty sure Railway gives you a grace period before deleting your data, although I could be wrong, but I'm pretty sure your data is safe assuming you didn't take forever to pay the invoice Yea I'm absolutely lost on what the issue could be
Brody
Brody•11mo ago
build logs?
Pabs3
Pabs3OP•11mo ago
Would you happen to know how long that grace period is? I missed the emails and it looks to have been about a month 😦 one sec let me download them, they seem fine to me
Fragly
Fragly•11mo ago
not entirely sure 😬
Brody
Brody•11mo ago
theres some funky stuff going on here fragly do you wanna take it from here?
Fragly
Fragly•11mo ago
I'm not entirely sure of myself on this one, I'd prefer spectating
Brody
Brody•11mo ago
@Pabs3 would you happen to have a nixpacks.toml or railway.json in your project?
Pabs3
Pabs3OP•11mo ago
Yes I have a nixpacks.toml
Brody
Brody•11mo ago
send it please
Pabs3
Pabs3OP•11mo ago
Brody
Brody•11mo ago
okay going to go off on a tangent here, this is not the first time i have seen this nixpacks.toml file break stuff. is your medusa project based off of some existing project that already had this file?
Pabs3
Pabs3OP•11mo ago
I believe I did copy over the file from an existing project and not create a new file with the contents inside since they were identical when I first deployed to railway
Brody
Brody•11mo ago
do you know where that original nixpacks.toml came from? or did you originally create it?
Pabs3
Pabs3OP•11mo ago
Yes I originally created it for a seperate project
Brody
Brody•11mo ago
have i helped you before?
Pabs3
Pabs3OP•11mo ago
No I just joined this discord server today from this issue I'm experiencing. Medusajs has documentation on deploying to railway so I'm sure you've helped others from that community
Brody
Brody•11mo ago
gotcha, thanks for that info, lets get back on track now do you use yarn or npm locally?
Pabs3
Pabs3OP•11mo ago
npm
Brody
Brody•11mo ago
does your project have a yarn lock file
Pabs3
Pabs3OP•11mo ago
indeed it does
Brody
Brody•11mo ago
does your project have a package lock file?
Pabs3
Pabs3OP•11mo ago
yes
Brody
Brody•11mo ago
what node version do you use locally?
Pabs3
Pabs3OP•11mo ago
18.13.0
Brody
Brody•11mo ago
do you have your engines.node set to 18 in your package.json?
Pabs3
Pabs3OP•11mo ago
my package.json does not currently have a reference to engines.node
Brody
Brody•11mo ago
go ahead and set that, then could you send a screenshot of that once done?
Pabs3
Pabs3OP•11mo ago
set it to 18.13.0?
Brody
Brody•11mo ago
just 18
Pabs3
Pabs3OP•11mo ago
No description
Brody
Brody•11mo ago
perfect, now delete the nixpacks.toml and the yarn lock file, then push the changes to github
Pabs3
Pabs3OP•11mo ago
Ok one sec
Brody
Brody•11mo ago
wait, remove the package manager from this
Pabs3
Pabs3OP•11mo ago
ok Ok just pushed those changes Still getting an error starting the server
Brody
Brody•11mo ago
build logs please
Brody
Brody•11mo ago
didnt you say you have a package lock file?
Pabs3
Pabs3OP•11mo ago
Yes I do
No description
Brody
Brody•11mo ago
its being gitignored
Pabs3
Pabs3OP•11mo ago
I see let me fix that
Pabs3
Pabs3OP•11mo ago
Pabs3
Pabs3OP•11mo ago
Looks like another medusa user is currently experiencing the same error
Brody
Brody•11mo ago
where?
Pabs3
Pabs3OP•11mo ago
on the medusa server. Almost identical logs with the only error being the server failing to start. Not sure how to copy a link to that thread here
Brody
Brody•11mo ago
copy paste?
Pabs3
Pabs3OP•11mo ago
lol didnt see the option to copy the link: https://discord.com/channels/876835651130097704/1196848130939957248 Ok looks like it was an issue on the medusa side. Thank you both for your time into helping me look into this. I'm now successfully deploying and back online with all of my data!
Brody
Brody•11mo ago
im sorry i got pulled away, but im happy you where able to solve it, would you mind telling what fixed it for anyone who sees this thread in the future?
Pabs3
Pabs3OP•11mo ago
Yes I was running some outdated packages so a simple package update fixed it.
Brody
Brody•11mo ago
awsome, thanks for the info but for the record, that nixpacks.toml file was also really not helping either 😆
Pabs3
Pabs3OP•11mo ago
I see. I missed the part where adding that file was optional in medusajs' documentation on deploying to railway. https://docs.medusajs.com/deployments/server/deploying-on-railway
Brody
Brody•11mo ago
oh wow, they should remove that entire section youre in their discord, can you ask them to remove it?
Pabs3
Pabs3OP•11mo ago
Yes I'll make the suggestion but not entirely sure why. Can you help me understand what the issue is?
Brody
Brody•11mo ago
as long as the repo is correctly setup with the appropriate lock file (not two lock files) and the engines.node is set to the desired major node version, there is zero need for that nixpacks.toml file
Want results from more Discord servers?
Add your server