4 hours ago
Project: vivacious-vibrancy
Service: invigorating-freedom
Environment: production
After my trial expired, my account switched to the Free plan. My deployment now fails with:
"Free plan deployments must be serverless. Please go to your service settings and turn on the serverless flag."
Serverless (App Sleeping) is already enabled in Settings > Deploy. I've tried:
- Regular Redeploy
- "Deploy latest commit" via the command palette (Ctrl/Cmd+K)
Both attempts still fail with the same error.
I have a Volume (invigorating-freedom-volume) attached to this service with important data on it that I need to download. Could you please manually trigger a deployment on your end, or let me know what else might be causing this?
Thanks!
4 Replies
Status changed to Awaiting Railway Response Railway • about 4 hours ago
3 hours ago
You can download your volume data right now without a running deployment using the Railway CLI. Run railway volume browse / to open an interactive file browser, or railway volume files download / ./local-backup to pull everything locally.
For the deployment failure, we can confirm serverless is enabled on the service. Upgrading to the Hobby plan ($5/mo) removes the serverless requirement entirely and would let the service deploy normally.
Status changed to Awaiting User Response Railway • about 3 hours ago
angelo-railway
You can download your volume data right now without a running deployment using the Railway CLI. Run `railway volume browse /` to open an interactive file browser, or `railway volume files download / ./local-backup` to pull everything locally. For the deployment failure, we can confirm serverless is enabled on the service. Upgrading to the Hobby plan ($5/mo) removes the serverless requirement entirely and would let the service deploy normally.
3 hours ago
Thanks for the reply! I just tried both commands again on my end:
railway volume browse /
Result:
"Service invigorating-freedom has no active deployment in environment production. Deploy or restart the service before using file commands."
So it seems the CLI still requires an active deployment on my account, contradicting what you mentioned. Could you double check on your end? Project: vivacious-vibrancy, service: invigorating-freedom.
Also, regarding serverless — I have it enabled, but every deploy attempt fails with:
"Free plan deployments must be serverless. Please go to your service settings and turn on the serverless flag."
even with the flag on and using "Deploy latest commit". This seems to be blocking me from getting the service running at all, which in turn blocks the volume file commands too.
Status changed to Awaiting Railway Response Railway • about 3 hours ago
3 hours ago
You're right that the CLI volume commands require an active deployment, so those won't work here. Apologies for the incorrect guidance on that.
We can confirm serverless is enabled on the service, but the deploy is still being rejected at the plan-limits check. Since deploys are blocked and the volume commands depend on a running deployment, upgrading to the Hobby plan ($5/mo) at https://railway.com/workspace/plans would resolve both problems at once: it removes the serverless requirement so the service can deploy normally, which also unblocks the CLI volume commands for downloading your data.
Status changed to Awaiting User Response Railway • about 3 hours ago
angelo-railway
You're right that the CLI volume commands require an active deployment, so those won't work here. Apologies for the incorrect guidance on that. We can confirm serverless is enabled on the service, but the deploy is still being rejected at the plan-limits check. Since deploys are blocked and the volume commands depend on a running deployment, upgrading to the Hobby plan ($5/mo) at https://railway.com/workspace/plans would resolve both problems at once: it removes the serverless requirement so the service can deploy normally, which also unblocks the CLI volume commands for downloading your data.
2 hours ago
I understand upgrading would fix it, but I specifically need this as a free plan user just to recover my data not planning to become a paying customer. Since you've confirmed this is a bug on your end (serverless enabled but still rejected), is there any way to get a one-time manual deploy or temporary unlock without upgrading? I just need to pull data off the volume once.
Status changed to Awaiting Railway Response Railway • about 2 hours ago