a year ago
Project id > feb1b71b-30b0-4504-8fe3-076c808f4942
50 Replies
I have 2 instances > one for dev other for prod... dev instance works fine prod is having issues
a year ago
Same here
a year ago
i get this error:"ERROR: failed to build: failed to receive status: rpc error: code = Unavailable desc = error reading from server: EOF"
My build get suck at [auth] sharing credentials for production-us-east4-eqdc4a.railway-registry.com ✔ 0ms
one diffference I can see is my dev instance is on southeast and prod is on us-east. southeast is working fine
Yes, it seems to be a problem with the region, in my case I have the production in the region down
nice! i just tried US west and it was working - thanks for the help y'all. pretty new to infra/deployment and probably wouldn't have thought to change regions without reading the thread 🙂
a year ago
Yeah my builds are taking quite long as well
a year ago
stuck on the [auth] sharing credentials for production-us-east4-xxxxxxx.railway-registry.com step
a year ago
I am stuck in importing to docker
a year ago
are you guys still having the 'sharing credentials' bug? @Pankaj Dubey @develoPro.cl
a year ago
@Dreez @Jack-TitleAI @Dmitry ^
a year ago
My builds finally went through 🙂 Haven’t tested since tho
I am waiting for builds stuck on "sharing credentials for {url}" US East metal
Builds were started 8 min ago
for me it is stuck in deploy step for really long time, usually it's 2-3 minutes but now it's almost have an hour.
a year ago
I redeployed a project of mine in us-east and I also got stuck on the [auth} ... step, reported it to the team
a year ago
can you share your deploy region and your build logs?
a year ago
so we can see if it's related
a year ago
same issue, except all past builds dont work anymore as well
this is crazy
+1 for this, issue must be newer than 70 minutes when my last build got through
a year ago
same region?
a year ago
I will also escalate this thread
a year ago
!t
a year ago
This thread has been escalated to the Railway team.
Status changed to Awaiting Railway Response medim • 11 months ago
a year ago
While monitoring the stream processing logs, I observed multiple consecutive entries containing exactly the same vertex hash and timestamp values (see attached screenshot).
This behavior seems unexpected because:
- The
vertexfield (sha256:cf05ebcfad0e7cba6ec6e903dce...) repeats identically across all records. - The timestamps are very close (milliseconds apart), but all entries appear to be processed independently rather than batched.
- No meaningful variation exists in the content of each record aside from the timestamp fragment.
a year ago
any temp fixes during that global outage (which has not been reported for 14 hours now...)?
my whole app doesnt work right now
a year ago
even switching regions doesnt work anymore 🤷♂
The hiccup on US-East seems to be over, my build just got through. If you were stuck on the [auth] sharing credentials step, I suggest you recheck your builds 🙂
a year ago
never mind changing region to california works (tho build times are crazy long) BUT I'm hitting a bunch of 499, 502 errors and even if I successfully ping the server it cant do any HTTP requests on its own
a year ago
Hello, ksawery29 , do you mind opening your own help thread if you didn't do so already? Yours seems to be a more serious standalone issue. Maybe ping medim to escalate that thread to the team.
a year ago
yep - took 19m but mine just went through
a year ago
Hello all,
We are looking into the stuck / slow builder issues right now.
Sorry for the troubles and thank you for your patience.
Status changed to Awaiting User Response Railway • 11 months ago
a year ago
@here according to #🚨｜incidents this has been fixed
Can you guys see if your builds are passing?
a year ago
Already worked
Status changed to Awaiting Railway Response Railway • 11 months ago
a year ago
Experiencing a (related?) issue of databases not being deployed, regardless of region.
neall
Experiencing a (related?) issue of databases not being deployed, regardless of region.
a year ago
Please open your own thread for that.
Status changed to Awaiting User Response Railway • 11 months ago
Status changed to Solved brody • 11 months ago