a month 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!
6 Replies
Status changed to Awaiting Railway Response Railway • 27 days ago
a month 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 • 27 days 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.
a month 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 • 27 days ago
a month 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 • 27 days 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.
a month 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 • 27 days ago
mellstroy1488-svo
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.
a month ago
Try disabling serverless, deploy, then enable it, and deploy.
a month ago
You haven’t run Deploy latest commit since switching to the Free plan. Your requests since then have all been regular Redeploy attempts, which reuse the old settings with Serverless disabled.
Open invigorating-freedom in production, press Ctrl/Cmd+K, and select Deploy latest commit. Please do this after 8 PM Amsterdam time, when the Free plan peak hours restriction ends.
Once the service is running, retry downloading your volume data.
Status changed to Awaiting User Response Railway • 27 days ago
20 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 • 20 days ago