`railway up`: 504 Gateway Timeout
I see a route propagation issue in #🚨｜incidents, however that was resolved ~16hrs ago.
28 Replies
Project ID:
ea673539-502e-4690-8fef-0503fa9123c9,9a3b5bb2-8030-44b3-9f17-1241b21bc364,840bb42c-cb06-4a6f-aa07-c5337c399cb2You might find these helpful:
- Railway CLI not working as expected - 409 Conflict Error
- railway up fails with 413 Request Entity Too Large
-
railway up raises Error: HTTP status client error (409 Conflict) for url (...)⚠️ experimental feature
dear god
everything is fine, calm down (freaks out)
real
don't you just love the vague error responses the CLI spits out?
yes
so i thought it was a me problem
you know, being on an alpha version of rlwy cli
and people hate on Go's error handling
it wasn't a me problem
idk whether or not to dm neb
because hes working hard
about improving error messages or about the API being down?
the second one
I'm sure the team knows their API is down
yep
thats why i didn't do it
this is bruh i cant even get my vars from cli i hope i can get them from dashboard
the blackboard fell off the wall
real
thankg od
lol manually specifying a port
cringe
wym manually
im pretty sure that variable doesn't even get 
a default which defaults to the same as whatever that thing is set to anyways
a default which defaults to the same as whatever that thing is set to anywaysyeah you're settling a port yourself in the service variables
cringe
use the random injected PORT
@Brody i solved it
why is there no error when you're not logged in to railway đź’€
fuck it im making that an issue
what? you wernt logged in?
i was i think i got logged out or something
i have no idea
confusing error messages
i know right
neb, the average user isn't gonna know what "failed to retrieve response body" means
Real