← Void · A-to-Mind · Fix an automation

n8n webhook 404 "not registered": test URL or production URL, and how to fix it

You see: 404 ยท webhook is not registered

What it means

n8n gives every Webhook node two URLs. The test URL only answers while the editor is listening for a test event; the production URL only answers once the workflow is active (published, in newer versions). A 404 nearly always means the sender is calling the one that is not listening right now.

How to fix it

  1. Open the Webhook node and compare its Test URL and Production URL with the URL the sending app is calling. The test one has /webhook-test/ in its path.
  2. For live traffic, put the Production URL into the sending app, then save the workflow and switch it to active (publish it, in newer n8n).
  3. For a test, click Listen for test event first and send within the listening window (about two minutes), then check the run in the editor.
  4. Check the HTTP method: the node only answers the method it is set to (GET, POST and so on). Production runs show in the Executions tab, not the editor.

If it keeps coming back

Self-hosted behind a proxy: if the URLs n8n shows point at localhost or the wrong host, set the WEBHOOK_URL environment variable to your public address, and make sure the proxy forwards both /webhook/ and /webhook-test/.

Still stuck? Ask Void, free

Paste the error and what the automation does. Void names the likely cause and the fix, in seconds, no account.

Ask Void about this error

Or have it fixed: $25

One broken automation, diagnosed and repaired, with proof it runs again. Reply to the receipt with what stopped.

Get the One-Time Fix

The One-Time Fix covers one workflow. What you send and what you get back.

Sources