20 days ago
Hi, for my server setting (server is proud-patience)
i have self-hosted n8n and I have used a custom URL which is working.
but when I use the webhook module on n8n (see attached screenshot), the webhook URL is still railway URL.
https://primary-production-b9b88.up.railway.app/webhook/
I saw other people who self-hosted n8n managed to change the webhook to their own custom URL as well.
Is there any way in railway I can set up that gives me the custom URL for the n8n webhook?
my custom url (in railway) is n8n.dditech.ai
Thanks for help.
Attachments
4 Replies
20 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!
20 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 brody • 20 days ago
20 days ago
Are any of your environmental variables set to this Railway URL? Perhaps ${{RAILWAY_PUBLIC_DOMAIN}}?
20 days ago
Hey, just to add to Sam's response, it is likely the WEBHOOK_URL variable being the culprit.
If it's set to ${{RAILWAY_PUBLIC_DOMAIN}} or not set at all, n8n will use Railway's generated domain for webhook URLs.
Change it to:
WEBHOOK_URL=https://n8n.dditech.ai
Then redeploy.
The webhook URLs in n8n should then show your custom domain instead of the Railway URL.
sarangsohail
Hey, just to add to Sam's response, it is likely the WEBHOOK_URL variable being the culprit.If it's set to ${{RAILWAY_PUBLIC_DOMAIN}} or not set at all, n8n will use Railway's generated domain for webhook URLs.Change it to:WEBHOOK_URL=https://n8n.dditech.aiThen redeploy.The webhook URLs in n8n should then show your custom domain instead of the Railway URL.
19 days ago
Thanks to both you and Sam.
I have checked that the webhook_url is already set to the custom url. It has been this way since I started the railway account.
But in n8n the webhook url is still {{railway_public_domain}} url.
Is there a safe approach to fix this issue? (from anyone or Railway)
Appreciate any help.
Attachments