Railway issue with PRODUCTION Webhook

Hi, I have again issue with Railway, it looks like the production webhook URLs does not work, the TEST one is ok. I receive a 404 error, it looks like is not accessible.

BTW if I run the same exact same test with a server I have in Elestio I have a successfull response.

Does have anyone a server with Railway? Maybe it’s just a variable or config setting to change?

Thanks

Giampiero

Information on your n8n setup

1 Like

Hello, @gpbonifazi

This is quite strange. Does this happen even when using a different webhook node? In railway, what are sure env vars set as?

Also are you seeing any errors in the logs at all?

I’ve used railway but can’t say I ever experienced this.

Best regards,

Samuel

I found what the problem was. The Railway server is built from a template with a webhook processor separated instance so the URL for webhook is different, for example is https://webhook-processor-production-0696.up.railway.app/webhook/your-service instead of https://primary-production-0696.up.railway.app/webhook/your-service this only apply to the PRODUCTION url not the webhook node.

Follow-up: if you have this setup in Railway you have to change the WEBHOOK_URL variable of your Primary to point to the Webhook Processor.

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.