Railway•3mo ago

Railway up error

error sending request for url operation timed out

Solution:

This was definitely our fault. I've rolled out a fix for it

Jump to solution

30 Replies

Percy•3mo ago

Project ID: e3db76cc-8c7e-48bf-b655-0bbd0f48c388

igorOP•3mo ago

e3db76cc-8c7e-48bf-b655-0bbd0f48c388

Dylpickle•3mo ago

same issue here this looks like an incident

Run railway up -d -s "service 1"
  
Indexing...
Uploading...
error sending request for url (https://backboard.railway.app/project/--/environment/--/up?serviceId=--): operation timed out
Caused by:
    operation timed out
Error: Process completed with exit code 1.

Run railway up -d -s "service 1"
  
Indexing...
Uploading...
error sending request for url (https://backboard.railway.app/project/--/environment/--/up?serviceId=--): operation timed out
Caused by:
    operation timed out
Error: Process completed with exit code 1.

igorOP•3mo ago

Damn, I've tried everything

Dylpickle•3mo ago

I don't think you can do anything about it

igorOP•3mo ago

Just wait i guess

Brody•3mo ago

what is the size of your projects?

Dylpickle•3mo ago

same size it was yesterday? <40mb

Brody•3mo ago

try smaller

Dylpickle•3mo ago

i can't really i've been deploying the same project for almost a year

igorOP•3mo ago

Mine weighs less than 1mb, i deployed yesterday and it was fine now says Failed to upload code with status code 504 Gateway Timeout

Dylpickle•3mo ago

╰─ git count-objects -vH
count: 3656
size: 18.71 MiB
in-pack: 22709
packs: 12
size-pack: 187.81 MiB
prune-packable: 65
garbage: 0
size-garbage: 0 bytes

╰─ git count-objects -vH
count: 3656
size: 18.71 MiB
in-pack: 22709
packs: 12
size-pack: 187.81 MiB
prune-packable: 65
garbage: 0
size-garbage: 0 bytes

20~ MB too big? I really hope not... @Brody

Brody•3mo ago

no, it should be 40MB iirc

Dylpickle•3mo ago

any ideas why its getting a operation timed out?

Brody•3mo ago

what does size-pack mean?

Dylpickle•3mo ago

not sure

          size: disk space consumed by loose objects, in KiB (unless -H is
           specified)

           size-pack: disk space consumed by the packs, in KiB (unless -H is
           specified)

          size: disk space consumed by loose objects, in KiB (unless -H is
           specified)

           size-pack: disk space consumed by the packs, in KiB (unless -H is
           specified)

Brody•3mo ago

run railway up in verbose mode please

Dylpickle•3mo ago

howso

Brody•3mo ago

with the verbose flag

Dylpickle•3mo ago

Run railway up -d -s "service 1" --verbose  
Indexing...
railway up
service: -
environment: -
bytes: 5280872

Run railway up -d -s "service 1" --verbose  
Indexing...
railway up
service: -
environment: -
bytes: 5280872

so 5.2MB should be well within the size

igorOP•3mo ago

That worked?

Dylpickle•3mo ago

Duchess•3mo ago

New reply sent from Help Station thread:

Same happening to me. Agree this looks like an incident:IndexedCompressed [====================] 100% railway upservice: b4a880db-6e93-472f-b26b-bc5bedde2703environment: 35c3822b-fb5b-4bfe-a715-fa7e23fe38d3bytes: 172390url: https://backboard.railway.app/project/724daebe-1427-4be4-ab74-de262b1ce4e2/environment/35c3822b-fb5b-4bfe-a715-fa7e23fe38d3/up?serviceId=b4a880db-6e93-472f-b26b-bc5bedde2703error sending request for url (https://backboard.railway.app/project/724daebe-1427-4be4-ab74-de262b1ce4e2/environment/35c3822b-fb5b-4bfe-a715-fa7e23fe38d3/up?serviceId=b4a880db-6e93-472f-b26b-bc5bedde2703): operation timed out

You're seeing this because this thread has been automatically linked to the Help Station thread.

Dylpickle•3mo ago

@Brody can we push this up the chain?

Duchess•3mo ago

New reply sent from Help Station thread:

same issue, timing out with size 9754414 (9.7MB)

You're seeing this because this thread has been automatically linked to the Help Station thread.

nickmacavoy•3mo ago

We can't deploy either – and for the last hour. Project 3c08e827-8d73-4a37-bbe9-9af9757bd354 Ping please team. We have a production deploy that we're unable to do. We're in Australia so it's still business hours

JustJake•3mo ago

Acknowledged. Looking into this

maddsua•3mo ago

Hey folks, I was getting the same issue when I tried to build the cli with rustc on msys2 ucrt64. It could be that some dependencies are broken. @Shippuden is this happening on windows?

Solution

JustJake•3mo ago

This was definitely our fault. I've rolled out a fix for it

igorOP•3mo ago

Yes, windows, but I haven't installed dependencies since the last pull, everything was working fine untill yesterday, I can't deploy any proyect I have Is working now

Gaming

Programming

Railway up error