a day ago
I am just redeploying the last version of my code that was successfully built and deployed only to account for a variable
Attachments
6 Replies
Status changed to Awaiting Railway Response Railway • 1 day ago
a day ago
Are there any errors in the Build Logs? Also try Redeploy Latest Commit from the Command Palette (Ctrl/Cmd+K) as the Diagnose said
mayori
Are there any errors in the Build Logs? Also try Redeploy Latest Commit from the Command Palette (Ctrl/Cmd+K) as the Diagnose said
a day ago
There are no errors in build logs. Also, I tried redeploying latest commit as suggested. Still the same.
kepee24
There are no errors in build logs. Also, I tried redeploying latest commit as suggested. Still the same.
a day ago
Attachments
a day ago
This must be related to the railway build daemon.
“buildkitd.sock: use of closed network connection”
a day ago
I'm seeing other reports with the same error you're encountering. I'll escalate this to the team
a day ago
This is on our side. There is an active incident on our build infrastructure (https://status.railway.com/incident/ILLVW9WG, "Builds failing in US West"): builds are failing before any of your build steps run, with the build daemon connection dropping or the build machine never coming up, which is exactly what your deployments show. Your source, build configuration and dependencies are not at fault, and nothing needs to change on your end.
Running services are not affected. A fresh deployment of the same commit may get through in the meantime; otherwise please follow the status page for the all-clear, and redeploy once it is posted.
Status changed to Awaiting User Response Railway • about 24 hours ago