a month ago
hi, I had this all working perfectly connected to an n8n with a bunch of automations working find. particularly one of them. it stopped working like a week ago. now I can't get there. trying to trouble shoot since and still no luck
I'm brand new to this, and not even sure where to start.
and claude and chat gpt says the error is on railways end not anything I can change. so I'm emailing you to help me out.
thank you,
JEFF
1 Replies
Status changed to Open Railway • about 1 month ago
a month ago
First thing I’d check is whether n8n is actually receiving the request, or if the webhook URL changed.
In n8n, open that workflow, copy the Production URL from the trigger, and compare it with whatever app/service is calling it. I’ve seen people lose time because the caller is still hitting an old webhook, or a test URL instead of the production one.
Then open the Railway service logs at the exact time the automation should run. If the request is reaching n8n, you should see either the webhook hit or the error there.
Also check WEBHOOK_URL, N8N_HOST, and N8N_PROTOCOL in Railway. If you changed domains, redeployed, restored from backup, or changed the public URL, n8n can keep generating/expecting the wrong webhook URL.
If you paste the actual log line/error, it’ll be way easier to tell if this is Railway networking, n8n config, or just the upstream automation calling the wrong endpoint.