3 months ago
I returned to railway after a whille and I found out that the n8n instance got remvoed and i can't access my workflows now. how i can recover it?
6 Replies
3 months 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!
3 months ago
You just need to deploy it again. Click that purple button or any or the most recent working deploy and click to redeploy it.
If you want to start fresh, make sure to deploy from this template: https://railway.com/deploy/n8n-with-workers
testuser123
You just need to deploy it again. Click that purple button or any or the most recent working deploy and click to redeploy it.If you want to start fresh, make sure to deploy from this template: https://railway.com/deploy/n8n-with-workers
3 months ago
Thank you! btw By clicking the "deploy the image" purple button will it deploy it and also restore all my previous workflows?
3 months ago
====================
Starting Healthcheck
====================
Path: /healthz
Retry window: 5m0s
Attempt #1 failed with service unavailable. Continuing to retry for 4m49s
Attempt #2 failed with service unavailable. Continuing to retry for 4m38s
Attempt #3 failed with service unavailable. Continuing to retry for 4m33s
Attempt #4 failed with service unavailable. Continuing to retry for 4m19s
Attempt #5 failed with service unavailable. Continuing to retry for 4m1s
Attempt #6 failed with service unavailable. Continuing to retry for 3m35s
Attempt #7 failed with service unavailable. Continuing to retry for 2m55s
Attempt #8 failed with service unavailable. Continuing to retry for 2m15s
Attempt #9 failed with service unavailable. Continuing to retry for 1m35s
Attempt #10 failed with service unavailable. Continuing to retry for 55s
Attempt #11 failed with service unavailable. Continuing to retry for 15s
1/1 replicas never became healthy!
Healthcheck failed!
now I'm trying to redeploy it but it seems that it can't establish connection. what can be the solution please?
Attachments
3 months ago
nevermind! deployed the other containers linked to the other 3 services linked to the primary n8n then deployed it and worked fine
Status changed to Solved brody • 3 months ago