Changing test webhook url

Describe the problem/error/question

I want to change the url for testing webhooks. It seems like N8N_WEBHOOK and N8N_HOST is only affecting the production webhook url. I looked into env var reference and also source code and couldn’t find anything to change the domain for testing webhooks.

Information on your n8n setup

  • n8n version: 1.123.4
  • Database (default: SQLite): postgresql
  • n8n EXECUTIONS_PROCESS setting (default: own, main): queue
  • Running n8n via (Docker, npm, n8n cloud, desktop app): k8s
  • Operating system: EKS v1.33

It is not officially documented, but was mentioned by a n8n member here before:

This is for the path. I mean the domain.

Have you set WEBHOOK_URL ?
This should change the URL for test and production.
However, you cannot have two different domains set for production and test. but only two different endpoints with the already mentioned env variables.

I have set WEBHOOK_URL but it only affects the production URL, test domain is not changed. I don’t want different domains but I want the test to use the same domain as production.

WEBHOOK_URL does change the URL for test webhooks too.
Also, there is no know issue with version 1.123.4 regarding this env var.
Please share your setup configuration (docker compose or similar).

Also, consider updating to version 1.123.6 or 1.123.7 and see if the issue persists.

No it seems to be following N8N_EDITOR_BASE_URL. I can’t share my config but these two variables are both set (to different domains) since the webhook is available on the internet and the UI is internal.

Setting N8N_HOST also doens’t make a difference.

I will try to replicate this locally, so I can share the config here, but i’m not sure I have the time.

Anyways, I’m sure of the variable being set, I just checked with printenv command inside the pod.

Yeah, I am having the same issue. The production webhook URL changes (created another published route in the same tunnel configurations to have a publicly accessible domain), but the test URL remains the same (the one that is not public - is behind a Cloudflare zero trust access policy).

I tried different versions, but it won’t budge.