Builds are frequently failing due to failing to create snapshot
jamiemufu
PROOP

a month ago

Builds are failing

Failed to create code snapshot, Have to retry 4-5 times to get it to build. Unacceptable given that I can't even build concurrently across two environments for no reason anymore

$20 Bounty

8 Replies

Status changed to Awaiting Railway Response Railway about 1 month ago


jamiemufu
PROOP

a month ago

This is happening mostly with railway up it seems


jamiemufu
PROOP

a month ago

error sending request for url (https://backboard.railway.com/project/d30fd09b-4b8a-40bd-bf0c-78d575e1e2f6/environment/39e5c64f-6f02-4303-9e72-9a403355bfbc/up?serviceId=8431d465-0543-4abd-95de-8f2573b1194d)

Caused by:

0: client error (SendRequest)

1: connection error

2: received fatal alert: BadRecordMac

Error I get from railway CLI - not sure if related


jamiemufu
PROOP

a month ago

Still nothing? Absolutely absurd having to wait days when I cannot build to staging without having to manually watch and re-run 5 failed deployments


sam-a
EMPLOYEE

a month ago

Sorry for the delayed response here.

The BadRecordMac error you're seeing is a TLS handshake failure that happens during the code upload to our servers. This typically points to something interfering with the connection between your machine and our API.

A few questions to help narrow this down:

  1. Is this new behavior, or has it always been flaky? If it started recently, did anything change on your end (new VPN, network, OS update)?

  2. What's your network setup? Are you on a corporate network, using a VPN, or running any antivirus/firewall software that inspects HTTPS traffic?

  3. What region are you deploying from? (just curious if there's a geographic pattern)

  4. Does the same thing happen if you try from a different network? (e.g., mobile hotspot)

Also, could you run railway version and share the output? And if you're able to, try upgrading to the latest CLI with railway upgrade to rule out any client-side fixes we've shipped.


Status changed to Awaiting User Response Railway about 1 month ago


jamiemufu
PROOP

a month ago

This is new behaviour, occurs during railway up mostly.

No VPN 1Gig connection, and nothing blocking

Deploying to EU

Not checked from hotspot, but I can.

Railway version:

Current version: 4.37.2 (Homebrew)

Running: brew upgrade railway

Warning: railway 4.37.2 already installed


Status changed to Awaiting Railway Response Railway about 1 month ago


jamiemufu
PROOP

a month ago

Also happens on both mac and windows, seperate machines, one wireless and the other hard wired


a month ago

The BadRecordMac error is a TLS issue originating from the client side, not from our infrastructure. We haven't seen this reported elsewhere, which points to something specific to your environment. We'll open this up to the community to help dig into what might be causing it.


Status changed to Awaiting User Response Railway about 1 month ago


Status changed to Open Railway about 1 month ago


I'd try manually sending the GraphQL request through an API client (or CURL) to further debug connection issues.


Welcome!

Sign in to your Railway account to join the conversation.

Loading...