a month ago
Hello Railway Team,
I am currently on the Hobby Plan, which should include up to 5GB of storage. However, my Postgres volume is stuck at 100% capacity (500MB limit) and I cannot find an option in the Settings to increase it manually.
This has caused my n8n instance to crash with a "No space left on device" error during migrations.
Could you please help me increase the volume size for my
postgres-volumeto 2GB or 5GB so I can resume my work? I am happy to pay for the additional usage as per the Hobby plan terms, but I don't need the Pro plan yet.Service: Postgres Environment: production Error: could not extend file: No space left on device
Thank you!
3 Replies
a month ago
Hobby plan volumes support up to 5GB and can be resized by clicking on the volume in your project canvas, then using the "Live Resize" button in the volume settings. Since your volume is at 100% capacity, the resize will be performed offline with a brief restart to run data integrity checks. More details are in our volumes documentation.
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
I have the same issue. But mongodb, I updated the size, restarted etc.. but crashes after a moment or two. Would just start over but would like to recover the contents of the db if possible.
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
If your MongoDB volume is still crashing after resizing and restarting, the filesystem may not have extended properly to use the new space. Please open a separate thread with your project link so we can investigate your specific service.
For recovering your data, check your MongoDB service's Backups tab to see if any manual or scheduled backups exist that you can restore from. More details on restoring backups are in our backups documentation.
If you have a specific service you would like us to look at, please send a link to it. .
Status changed to Awaiting User Response Railway • about 1 month ago
a month 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 • 30 days ago