a month ago
Hi Railway Support,
I'm experiencing a persistent database connection error even after upgrading to Pro Workspace. My service cannot connect to the database due to a quota error.
Project Details:
Project ID: d52a2b19-f330-414d-8c53-e587c073ec3b
Environment: production
Service: web (Node.js Telegram bot)
Error Message:
error: Your project has exceeded the data transfer quota. Upgrade your plan to increase limits.
What I've tried:
Upgraded my plan to Pro Workspace
Restarted the service multiple times
Verified the plan upgrade is active in billing
The error persists when the service attempts to connect to the PostgreSQL database. This appears to be an infrastructure-level issue, as the quota flag has not been reset despite the plan upgrade.
Could you please manually reset the data transfer quota flag for this project?
Thank you, roy shavit
3 Replies
a month ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open Railway • about 1 month ago
a month ago
First thing I’d check is whether the upgraded Pro plan is on the exact workspace that owns this project. It sounds obvious, but this error can keep showing if the project is still under a different/free workspace or if the DB service is in another environment/workspace than the app you upgraded.
After confirming that, I’d redeploy, not just restart, both sides:
- redeploy the Postgres/database service
- redeploy the
webservice after that - check the newest deploy logs for the same quota message
If the message is still in the latest deployment logs after both services were redeployed under the Pro workspace, then yeah, that’s probably a Railway-side quota/account state issue and only staff can clear it.
For the support ticket, I’d include:
- project ID
- database service ID too, not only the web service
- latest deployment IDs after the Pro upgrade
- exact timestamp of the error after redeploy
- screenshot/confirmation that the project’s workspace is Pro
I wouldn’t delete/recreate the database volume as a “fix” here. If you need a workaround and the DB can still be reached somehow, take a dump first, then restore into a fresh DB inside the confirmed Pro workspace.
a month ago
two branches depending on where the error is showing up.
if it's in railway's deployment logs (web or postgres container), it usually means the pro upgrade got applied to a different workspace than the one holding your project. pro benefits don't cross workspaces.
fix: project settings → general → transfer project → pick the upgraded workspace, then redeploy. the quota flag clears on the next deploy.
if the project is already in the upgraded workspace and the flag sticks, that's a stuck server-side state — tag @brody.
if the error is from your bot's code (not railway's logs), the wording is misleading — it's coming from a library or external api you're calling, not railway. grep your deps for "data transfer quota".
quickest tell: railway-generated quota errors appear in the deployments panel as system messages, not your stdout.