2 years ago
Hello,
My website crashes every morning. I deploy changes, it works, then it crashes the next day. This happens every morning. My website is a vercel project with two apps. I get this error everytime.
[global-color="primary"]{ color: #0a66c2 !important;}[global-color="secondary"]{ color: #ffffff !important;}[global-color="text"]{ color: #2f373d !important;}[global-color="dark"]{ color: #000000 !important;}[global-bgcolor="primary"]{ background: #0a66c2 !important;}[global-bgcolor="secondary"]{ background: #f2effd !important;}[global-bgcolor="dark"]{ background: #171718 !important;}
/app/apps/publish-section/dist/index.js:23781
throw new ApiException(message, status, response, headers, null);
^
ApiException [Error]: An unexpected server error occurred.
at throwException (/app/apps/publish-section/dist/index.js:23781:11)
at processFiles2 (/app/apps/publish-section/dist/index.js:24315:12)
at /app/apps/publish-section/dist/index.js:24294:12
at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
isApiException: true,
status: 500,
response: '',
headers: {
date: 'Sat, 30 Mar 2024 09:58:08 GMT',
'content-length': '0',
connection: 'close',
'cf-ray': '86c73d4b3d40ec27-SEA',
'cf-cache-status': 'DYNAMIC',
vary: 'Accept-Encoding',
'report-to': '{"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v4?s=5sT3oKDEbnkzq4em7b9WzUZRxiUWBSdj0JdYM4lGWXTHHglp2%2B8Eya%2F%2FMyIeVU432difa4hQplrt8KriJa%2BcbdKGnMsDsIicGO%2Fqd3IanroPDSDd%2FPE02ZfUCzHLE%2B1kPcC9RoBYkg%3D%3D"}],"group":"cf-nel","max_age":604800}',
nel: '{"success_fraction":0,"report_to":"cf-nel","max_age":604800}',
server: 'cloudflare',
'alt-svc': 'h3=":443"; ma=86400'
},
result: null
}
Node.js v18.18.2
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 1.
ⓘ Deployment information is only viewable by Project members and Railway admins.
10 Replies
2 years ago
I have to restart that deployment to get it fixed. Does anyone have a fix for this issue?
2 years ago
Looks like your app is crashing because it couldn't talk to some external API? can you please add more details as to why it's crashing?
2 years ago
Hey Brody,
Thank you for getting back to me. My question is that it works, for all endpoints, then crashes without me doing anything. Why work at all if it can't talk to an external API ?
I am thinking maybe because the nodejs versions are different.
2 years ago
What version are you running locally? Railway uses node 18 by default and you can change this by setting your engines.node in your package.json to something else like 20
2 years ago
locally I am running version 20, I can see that the railway is running 18, let me update the version to 20 and hopefully this doesn't restart tomorrow :-)
Thank you.
2 years ago
Brody, so I updated the node version. It crashed again, this time in the afternoon
2 years ago
I would recommend adding more verbose logging to help figure out why your code is crashing, without such logs there's not much I can help with.
Status changed to Solved Railway • about 2 years ago
2 years ago
Can you please check discord. I sent you a private DM. I know you don't work for railway.
2 years ago
Let's keep this chat here please, Do not DM people without permission, especially cross-platform.
2 years ago
Cool. Your responses didn't help me in any case regardless. Thank you for trying. I will see assistance somewhere else.