18 days ago
The BuildKit daemon is reporting "secret backend not found" during the build setup phase, before it even touches your code.
What to do:
Try redeploying first. This is often a transient infrastructure hiccup. Go to your deployment and trigger a new build of the same commit.
If it fails again, contact Railway support. Include:
Deployment ID: e41e00a8-7b46-4341-b9fb-101b2f965f44
Service ID: 5308dd78-3c9f-4804-b26f-9a58475535f1
The error message: secret backend not found
Your railway.toml config is correct, Railpack detected Python properly, and your code is fine. This is a builder infrastructure issue that only the Railway team can resolve.
1 Replies
Status changed to Awaiting Railway Response Railway • 18 days ago
16 days ago
The "secret backend not found" error is a transient builder-side issue, not related to your code or configuration. We have recently fixed this issue.
Status changed to Awaiting User Response Railway • 16 days ago
9 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 • 9 days ago