2 months ago
Subject: Service startCommand corrupted — backend crash loop (base64: invalid input)
Message:
Project: courteous-perception (508f431d-8d42-4bcc-87e3-a99a15aa80dc)
Service: optionpilot-backend-sV-u (c3c8af76-2d92-43c5-92d3-b10b9914d631)
Environment: production (6733fddf-f2f4-49e8-a676-e58b5d907a46)
My source code is embedded in the service's deploy.startCommand field as a base64 payload (Function-type service, deployed via Claude/Railway agent artifact deploy). An automated edit attempt corrupted this base64 payload. The service is now crash-looping with the error:
base64: invalid input
This has taken my backend fully offline. Please restore this service's configuration (specifically the startCommand field) from the last known-good backup/snapshot before this corruption occurred (prior to approximately 2026-07-27 01:33 UTC).
Thank you.
1 Replies
Status changed to Awaiting Railway Response Railway • 2 months ago
2 months ago
The startCommand is a user-editable service setting, not something we maintain historical snapshots of, so there is no prior version to restore from our side. All the configuration changes on this service were made from your own account (via the agent), and the current startCommand is set to ./run.sh. You can update it directly in your service's Settings > Deploy section with the correct base64 payload and redeploy to bring the backend back online.
Status changed to Awaiting User Response mykal • 2 months ago
2 months ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 2 months ago