Skip to content
failing to deploy
photoandmore-dev
OP

24 days ago

Hello,

My service free120bot has been failing to deploy three times in a row.

The deployment stops less than a second after starting, at Build → Build image, with the diagnosis Infrastructure Error. No build logs are generated.

The service has been running for approximately 6–12 months. It is connected to the GitHub repository photoandmore-dev/free120bot, branch main, and uses the default Railpack builder with Python 3.11.15.

Previously, occasional deployment failures could be resolved by redeploying, but this time three consecutive redeployments have failed identically.

I also received your October 23 preliminary security incident report, which stated that my workspace was not classified as higher-risk.

Could you please investigate whether this service is affected by an infrastructure issue or any lingering effects of the October security incident?

Thank you.

Solved

1 Reply

Status changed to Awaiting Railway Response Railway • 24 days ago


dizzydes90
EMPLOYEE

24 days ago

Both recent deployments of free120bot failed before the build started, while loading the stored copy of your source code from an earlier deployment. That is why there are no build logs, and nothing about it points to your code, Railpack setup, or Python version.

This is an after-effect of the October 21 incident on older source snapshots: redeploying an existing deployment reuses that same stored copy, so each redeploy fails the same way. It isn't an indication that your workspace was compromised.

Starting a fresh deployment fixes it. Open the service, press Cmd+K (Ctrl+K on Windows) and choose Deploy Latest Commit, or push a new commit to main.


Status changed to Awaiting User Response Railway • 24 days ago


Railway
BOT

17 days 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 • 17 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...