Corrupted Service Configuration - n8n & Postgres - Help Needed to Preserve Volume

ashxen111
HOBBY

16 days ago

Hello,

My n8n service (ID: 98c8a164-...) and its Postgres database have entered a corrupted state after several configuration changes.

The Problem:

My n8n service is in a crash loop, unable to connect to the database.

My Postgres service is also unstable. Its logs are cycling between FATAL: no PostgreSQL user name specified and Skipping initialization.

The Goal:

I critically need to restore access to my n8n application. The most important thing is to preserve the data in the attached Postgres volume, as it contains all my workflows and credentials.

What I've tried:

I've spent the last day trying to fix the environment variables for both services, but it seems to have made things worse.

My Request:

Can you please help me reset the service configurations for my Postgres and n8n services to a clean, default state, while ensuring the existing volume for Postgres is preserved and correctly re-attached?

Thank you for your help.

Project ID: ac8d7c1f-07c6-46da-9e0b-f3b4681fe35b

$10 Bounty

2 Replies

Railway
BOT

16 days ago

Hey there! We've found the following might help you get unblocked faster:

If you find the answer from one of these, please let us know by solving the thread!


monuit
PROTop 5% Contributor

13 days ago

hey, so what you can actually do is just create a new postgres service, and mount the existing postgres volume to it. youd need to copy over the variables (i.e POSTGRES_PASSWORD, and POSTGRES_DB), and then point your n8n service's db connection vars to that new service.

if you delete an existing postgres service, it doesn't delete the volume, you have to delete the volume separately, but you can just re-mount them.


Loading...