a month ago
My web app is not getting a response, I need the service up again since every minute is down represents loss of money
Error: ERR_TIMED_OUT, took too long to respond
7 Replies
a month ago
Hey there! We've found the following might help you get unblocked faster:
If you find the answer from one of these, please let us know by solving the thread!
a month ago
Hello,
Your app seems to be having errors which are visible in the console. As this is an application issue I'll open this to the community for help!
Status changed to Awaiting User Response Railway • about 1 month ago
noahd
Hello,Your app seems to be having errors which are visible in the console. As this is an application issue I'll open this to the community for help!
a month ago
I'm no sure that these errors are from the app, it seem to be from the infrastructure (Railway), here are the logs:
TypeError: fetch failed
at node:internal/deps/undici/undici:14900:13
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async i (/app/.next/server/chunks/6223.js:1:235084)
at async Promise.all (index 5)
at async l (/app/.next/server/app/(store)/page.js:1:2672) {
digest: '2625441633',
[cause]: AggregateError [ETIMEDOUT]:
at internalConnectMultiple (node:net:1134:18)
at internalConnectMultiple (node:net:1210:5)
at Timeout.internalConnectMultipleTimeout (node:net:1742:5)
TypeError: fetch failed
at node:internal/deps/undici/undici:14900:13
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async i (/app/.next/server/chunks/6223.js:1:235084)
at async Promise.all (index 5)
at async l (/app/.next/server/app/(store)/page.js:1:2672) {
digest: '2625441633',
[cause]: AggregateError [ETIMEDOUT]:
at internalConnectMultiple (node:net:1134:18)
at internalConnectMultiple (node:net:1210:5)
at Timeout.internalConnectMultipleTimeout (node:net:1742:5)
at listOnTimeout (node:internal/timers:590:11)
at process.processTimers (node:internal/timers:523:7) {
code: 'ETIMEDOUT',
[errors]: [ [Error], [Error], [Error], [Error] ]
}
}
a month ago
I need the service up ASAP, I ask for the technical support from Railway @noahd since the issue comes from communication between services inside the infrastructure
a month ago
Seems like you have a network issue, API endpoint not responding. Have you checked endpoint url config to make sure you're using full url, no 'lcoalhost', and try using public url instead of railway's private url ?