5 days ago
I am deploying N8N, which has both Primary and Worker nodes. I am able to configure a Custom Domain for the Primary - no problem. But when I want to use that same domain for the Worker, it shows - not available?
Maybe I don't need it on the Worker? Am I misunderstanding the use of the Custom Domain? Is it possible this will be a recurring problem for other solutions (this is my first deployment / usage of railway).
8 Replies
5 days ago
Sorry, DNS in N8N setup here - I hit Reply too fast, before upload finished.
Attachments
5 days ago
The worker does not run a web service, so there is no need to add a domain to it.
Status changed to Awaiting User Response railway[bot] • 5 days ago
5 days ago
Thank you for that - of course, that makes total sense! The worker deployed just fine the next time I tried - but then failed again with the enotfound error (n8n.<mydomain> not found - attached)
Interestingly, I thought the DNS would refresh at some point and the Primary and Worker are both failing still. I have screenshots showing the instructions on Railway, and my setup on AWS Route 53 with the records. The record setup seemed a little suspect so since it was trying to connect to a subdomain of 'n8n.<mydomain>', I just went ahead and setup a record of 'n8n.<mydomain>' instead of '@' and now a ping to n8n.<mydomain> works great - but the primary still will not deploy.
Not sure why the '@' value was specified (maybe it resolves on some DNS services - just not AWS). Might be good to update the DNS instructions per service (e.g. n8n deploys need an n8n subdomain). But also - still can't deploy.
Status changed to Awaiting Railway Response railway[bot] • 5 days ago
5 days ago
So, interesting - after I pinged n8n.<mydomain>, I tried pinging with https:// as the railway project does and, of course, it did not connect. So, I'm putting the original DNS record with the '@' - exactly as the instructions say - hoping that somehow resolves eventually. But AWS propagates their DNS very quickly and I'm still not seeing a successful deploy. Not sure what next steps are and open to any / all suggestions.
Attachments
5 days ago
Okay, trying to be thorough, but not annoying, so forgive the multiple replies - https:// is resolving fine, I was just doing it wrong. You can't ping with https, but it did resolve to railway in the browser. But - still getting getaddrinfo ENOTFOUND https://n8n.smileyai.io from Railway when I try to deploy N8N.
All advice welcome.
Attachments
3 days ago
I started from scratch - tore it down, reset the project up and did the DNS right from teh begining, with only the n8n.<mydomain> - it's all good. Thank you for the patience.
Status changed to Solved smileyaiadmin • 3 days ago