Production webhook not work

[Marko_Yurtsiv]

Hello.

Can you please help? I’m having an issue with production webhook - it’s just not working, and I’m getting a 404 error at the webhook URL, as shown in the screenshot

So, in the test environment, everything works fine, there are no errors, everything is activated, but the trigger doesn’t work in production… in the test, everything is OK.

I have n8n installed in Kubernetes on GCP – but all configurations seem to work, there are no errors in the logs, and I can’t understand why the production workflow isn’t working.

Information on my n8n setup

• n8n version: 1.62.6
• Database (default: SQLite): Postgres
• n8n EXECUTIONS_PROCESS setting (default: own, main):
• Running n8n via (Docker, npm, n8n cloud, desktop app): Kubernetes (GKE)
• Operating system: Kubernetes (Linux)

[ria]

Hi @Marko_Yurtsiv

Thanks for posting here and welcome to the community!

Does the URL that’s giving the 404 contain the word “test” ? When switching to production the URL of the webhook node also changes → make sure to use this URL.

[talha]

Hi @ria

I am facing the exact same issue. The test URL works, but the production URL gives a 404.
The test URL is something like this (this works)
https://some-domain.com/webhook-test/f31230-416f-48db-bcf0

The production URL is like this (this gives 404)
https://some-domain.com/webhook/f31230-416f-48db-bcf0

I have not setup any webhook processor node separetely. Everything is running inside the n8n pod, and the behavior of n8n is being changed via environment variables.

The only thing I have configured for the webhooks is to add the WEBHOOK_URL, which is the custom domain I am accessing n8n on.

WEBHOOK_URL=https://some-domain.com

This is information on my setup

• n8n version: 1.62.6
• Database (default: SQLite): Postgres
• n8n EXECUTIONS_PROCESS setting (default: own, main):
• EXECUTIONS_MODE=queue
• Running n8n via (Docker, npm, n8n cloud, desktop app): Kubernetes (GKE)
• Operating system: Container Optimized OS (Linux)

[ria]

Hi @talha

Do you get anything in your logs? You could enable the debug log level to get more details on why the 404 is received.

Logs environment variables | n8n Docs