2 months ago
Dashboard is here: https://railway.com/project/c02ff7c5-4da1-47a0-b48b-9e7302c57864?
Im constantly getting network errors now. VERY frustrating.
i am running several services, i dont know which of them or if all of them are the issue.
Attachments
5 Replies
2 months ago
You're mentioning network errors, could you point me to the service running into that?
Status changed to Awaiting User Response Railway • 2 months ago
noahd
You're mentioning network errors, could you point me to the service running into that?
2 months ago
point as in give names? links?
I have several that work in tandem. So i dont know which is failing. I would focus on GridL API, GridL Frontend and Postgres instance first.
Attachments
Status changed to Awaiting Railway Response Railway • 2 months ago
2 months ago
Poked around a bit and it looks like the GridL frontend is having issues during SSE "GridlAuthError: fetch failed".
On top of that, you were hitting a Clerk rate limit which could be a part of that issue.
That exact error is:
⨯ Error [GridlAuthError]: fetch failed
at v (.next/server/chunks/ssr/[root-of-the-server]__93d8d195._.js:3:4677)
at async i (.next/server/chunks/ssr/[root-of-the-server]__3eb0288a._.js:1:4152) {
category: 'NETWORK_ERROR',
statusCode: undefined,
timestamp: '2026-03-11T17:42:44.637Z',
referenceCode: 'GRD-FE6C9D-FAA2',
digest: '214345464'
I also poked around the postgres instance and it looks perfectly fine. Due to volume of requests I can't really help debug this specific issue but its likely a misconfigured url of some kind.
Status changed to Awaiting User Response Railway • 2 months ago
noahd
Poked around a bit and it looks like the GridL frontend is having issues during SSE "GridlAuthError: fetch failed". On top of that, you were hitting a Clerk rate limit which could be a part of that issue. That exact error is: ⨯ Error \[GridlAuthError\]: fetch failed at v (.next/server/chunks/ssr/\[root-of-the-server\]\_\_93d8d195.\_.js:3:4677) at async i (.next/server/chunks/ssr/\[root-of-the-server\]\_\_3eb0288a.\_.js:1:4152) { category: 'NETWORK\_ERROR', statusCode: undefined, timestamp: '2026-03-11T17:42:44.637Z', referenceCode: 'GRD-FE6C9D-FAA2', digest: '214345464' I also poked around the postgres instance and it looks perfectly fine. Due to volume of requests I can't really help debug this specific issue but its likely a misconfigured url of some kind.
2 months ago
ok, this is helpful. I will go clear up any clerk issues now. I'll report back if issue persists. Thank you
Status changed to Awaiting Railway Response Railway • 2 months ago
2 months ago
where did you see that I was hitting a Clerk rate limit? just curious.
a month ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open Railway • about 1 month ago