Your Postgres volume is at 4996 MB out of 5000 MB, which is why the service is crashing. Your Pro plan supports volumes up to 1 TB, so you have plenty of room to expand. If the "Live Resize" button is not working, look for a "Grow" button instead (this appears when a previous live resize attempt failed) - the Grow operation requires a service restart to take effect. You can find the resize option in your Postgres volume's settings page. After the volume expands, redeploy the Postgres service if it does not recover on its own.

Update:

The manual backup is no longer available.

The Live Resize dialog opens, but I cannot proceed to increase the volume.

There is no "Grow" button in the postgres-volume settings.

Could you please check my project and help me increase the volume or recover the database?

Thank you.

We can see your Postgres volume is now 10 GB with ~5 GB used, so the disk-full condition has cleared. The resize completed but the Postgres service was stopped as part of the process, which is why it is currently offline. You can bring it back by triggering a redeploy from your Postgres service page in the project dashboard. Your data on the volume is intact.

Update:

The PostgreSQL volume was successfully resized from 5 GB to 10 GB.

Postgres, Redis, Worker, and Primary now all show Online.

However, n8n never finishes starting.

The n8n main page only shows:

"n8n is starting up. Please wait"

The Primary deployment logs show:

QueryFailedError: relation "IDX_credentials_entity_is_global" already exists

Migration:

AddPartialIndexForGlobalCredentials1784000000044

Could you please help repair the failed migration without deleting the existing database?

Having looked into this, the issue appears to be in your application code or configuration rather than the Railway platform itself, which puts it outside what Railway support can resolve directly.

This is exactly the kind of problem the Railway community is good at, so we'd like to open your thread as a community bounty. Railway pays a bounty to the community member who solves it, and threads like this usually get picked up quickly.

Opening it makes this entire thread public, including everything already posted. Nothing becomes public until you decide. Use the buttons below.

• Open to the community - Before you click, take a moment to edit or remove anything you'd rather not share. The thread becomes publicly visible right away.
• Keep it private and close the thread - Nothing becomes public. The thread closes, since this isn't something Railway support can take further.

Official Railway n8n template.

PostgreSQL and Redis are healthy.

n8n fails during startup migration:

AddPartialIndexForGlobalCredentials1784000000044

Error:

relation "IDX_credentials_entity_is_global" already exists

I need guidance on safely reconciling the migration state or accessing SQL to inspect the migrations table and the IDX_credentials_entity_is_global index.

You could extend the volume

If you can get into the database, i'd just drop that index with DROP INDEX IF EXISTS "IDX_credentials_entity_is_global";