a year ago
Hello, SOMEONE CAN HELP ME PLEASE!
I'm currently running a production deployment of n8n v1.94.0 on Railway under the project balanced-courtesy. I've followed all the necessary steps to expose production webhooks correctly:
- Successfully deployed the n8n instance.
- Set the environment variable
WEBHOOK_TUNNEL_URL=https://n8n-production-db8a.up.railway.app. - Enabled basic authentication.
- Activated the workflow and the webhook in n8n.
- Made multiple deployments and restarts to ensure the environment was properly refreshed.
Despite this, the Production Webhook URL always displays http://localhost:5678/... inside the n8n interface, and webhook POST requests return this error:
The requested webhook "POST activar-mcp" is not registered.
Hint: The workflow must be active for a production URL to run successfully.
This suggests n8n is not registering the webhook in production mode, even though the workflow is active and deployed, and WEBHOOK_TUNNEL_URL is set.
Can someone please check if there's something wrong with how Railway is passing the variable into the container? Or confirm if a specific build/restart method is required to make the webhook production URL take effect?
Thanks for your help.
Best regards,
Dietrich Truchsess
1 Replies
a year ago
Probably because you’re using WEBHOOK_TUNNEL_URL, which is mostly for local dev stuff (like when you’re tunneling with ngrok). In prod, you wanna use:
WEBHOOK_URL=https://n8n-production-db8a.up.railway.app
You may also wanna set:
N8N_HOST=n8n-production-db8a.up.railway.app
N8N_PROTOCOL=https
After that, redeploy the service and it should stop showing localhost:5678 and actually register the webhook correctly.