"n8n deployment crashed" error

filigree
HOBBY

15 days ago

Hi,
All services in the same project and environment (production, region us-west2). n8n cannot get DNS for redis.railway.internal, although Redis is in production, private networking is enabled, everything is as in the documentation. After several restarts and many hours, ENOTFOUND does not disappear. What to do?

$10 Bounty

4 Replies

Railway
BOT

15 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!

filigree
HOBBY

14 days ago

Thanks for the links.
I’m on the Hobby plan, all services are in the same production environment and region. Private networking enabled.
Still, n8n main instance cannot resolve redis.railway.internal (see attached logs: ENOTFOUND).
All variables are set properly, services restarted several times, issue persists. Docs say this should not happen on Hobby plan.
Please check DNS/overlay for my workspace.

filigree
HOBBY

14 days ago

Good afternoon.
I'm still getting stuck on n8n-main-instance. Is there a way to solve this issue without programming? If not, where exactly should I enter the js code?

ray-chen
EMPLOYEE

13 days 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 ray-chen • 13 days ago