After yesterday's crash cant deploy my app
alekszahariev
PROOP

2 months ago

Hello! After yesterday's crash i tried many things to deploy my NocoDB server and i can't.

It always crashes.

Can someone help me resolve this as soon as possible, because we use it for work.

Solved

61 Replies

2 months ago

Did you deploy a template or is this a custom service?


2 months ago

(refering to NocoDB)


alekszahariev
PROOP

2 months ago

Template


alekszahariev
PROOP

2 months ago

But this is very old for 1 year it was working perfect and from yesterday because it crashed i cant deploy it again


alekszahariev
PROOP

2 months ago

Screenshot_2026-04-28_at_11.21.33.png

Attachments


alekszahariev
PROOP

2 months ago

Screenshot_2026-04-28_at_11.21.46.png

Attachments


2 months ago

Ah I see, in that case you can go to the template you deployed and on the right you can select Get template help, this will request help from the template author (since this seems to be an issue with the template having broken or something)


alekszahariev
PROOP

2 months ago

Screenshot_2026-04-28_at_11.30.47.png

Attachments


2 months ago

ooh that doesn't look good


2 months ago

i dont know much (or anything for that matter) about NocoDB unfortunately so I can't help much here 🥲


alekszahariev
PROOP

2 months ago

is there railway support that can help with this?


2 months ago

yea someone who knows more about NocoDB might jump into this thread hopefully


2 months ago

in the mean time I have one idea


2 months ago

can you send a screenshot of the top of your settings of the nocodb service?


alekszahariev
PROOP

2 months ago

Yesa


alekszahariev
PROOP

2 months ago

Screenshot_2026-04-28_at_12.26.57.png

Attachments


alekszahariev
PROOP

2 months ago

I saw nocodb had update yesteraday and im trying to deploy with the latest version but still it crashes


2 months ago

oh so you edited the source image?


2 months ago

my theory was it was on the latest tag, and so upon redeploy it deployed a new version which might've not been compatible with the previous version causing the crash loop


alekszahariev
PROOP

2 months ago

ah so i should find the version it was working before?


alekszahariev
PROOP

2 months ago

It was on latest originally , yes


alekszahariev
PROOP

2 months ago

Should i deploy from backup?

Screenshot_2026-04-28_at_12.29.22.png

Attachments


2 months ago

oh neat, and yes, if i were in your shoes I'd find the version it was on before it started crashing


2 months ago

those only backs up the volume content, not the service settings or deployment environment


2 months ago

you'll want to see what date and time your last healthy deployment went out, use that to find what the latest version at the time was and then move back to that version


2 months ago

if you got it back on an the same version it used to be and it still crash loops then I'd recommend restoring a backup (cause the new version might've made the files unreadable for the old version, potentially)


alekszahariev
PROOP

2 months ago

Screenshot_2026-04-28_at_12.31.21.png

Attachments


2 months ago

yea, just find what version was latest 11 months ago


alekszahariev
PROOP

2 months ago

okay so im looking for the version 11 months ago


2 months ago

exactly


alekszahariev
PROOP

2 months ago

Not working, i will try deploying the backup


2 months ago

alright! hopefully that works


alekszahariev
PROOP

2 months ago

Here is something strange

Screenshot_2026-04-28_at_12.38.43.png

Attachments


alekszahariev
PROOP

2 months ago

Screenshot_2026-04-28_at_12.38.56.png

Attachments


alekszahariev
PROOP

2 months ago

Yesterday's backup is 3.34GB


2 months ago

was yesterday's backup made on the newer version?


alekszahariev
PROOP

2 months ago

Most likely. It's auto backup


2 months ago

the newer version must've made huge changes to how storage works, as for how it got to 3.4gb is beyond me


alekszahariev
PROOP

2 months ago

So i rolledback the nocodb version , mounted the old storage and it says "online" but still its not accessible.


alekszahariev
PROOP

2 months ago

Screenshot_2026-04-28_at_12.49.05.png

Attachments


2 months ago

any errors in logs?


alekszahariev
PROOP

2 months ago

no 0 errors


alekszahariev
PROOP

2 months ago

tried deploying with the new volume but gave error. Now trying to deploy again with the old volume and it gives error...


2 months ago

so upon deploy it had no errors, then the next deploy with that volume it got errors again?


alekszahariev
PROOP

2 months ago

yes


alekszahariev
PROOP

2 months ago

Now its online

Screenshot_2026-04-28_at_13.00.11.png

Attachments


alekszahariev
PROOP

2 months ago

but not accesible


2 months ago

that service is in a very unstable state wow


2 months ago

are you sure that is the correct version?


alekszahariev
PROOP

2 months ago

this is the old version i deployed 11 months ago


2 months ago

then I'm out of ideas


alekszahariev
PROOP

2 months ago

Screenshot_2026-04-28_at_13.02.48.png

Attachments


alekszahariev
PROOP

2 months ago

This is intresting


2 months ago

that is some odd ordering 🤨


2 months ago

probs just a UI issue


alekszahariev
PROOP

2 months ago

network is not started so thats why i cant connect.. anyway i will update if i find a solution


2 months ago

your serivce has healthcheck endpoints, I don't think it'd start if the network wasnt working


2 months ago

well, i guess considering your service is inaccessible, those healthchecks arent doing their job 😓


2 months ago

unless you removed the healthcheck endpoints


alekszahariev
PROOP

2 months ago

I fixed the issue .

Redeployed brand new nocodb. And just replaced the variables so its connected to the original database


2 months ago

Nice! Glad you got it working


Status changed to Solved dev 2 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...