error fix
n8n Webhook 404: Fix Wrong URLs, Inactive Workflows, and Proxy Routes
A 404 on an n8n webhook usually means the request is hitting the wrong URL, the wrong test or production mode, an inactive workflow, or a reverse proxy path that does not reach the Webhook node.
Independent third-party notes. n8n is a trademark of its owner and is referenced only for compatibility and troubleshooting context.
Quick Answer
A 404 on an n8n webhook usually means the request is hitting the wrong URL, the wrong test or production mode, an inactive workflow, or a reverse proxy path that does not reach the Webhook node.
Problem Pattern
The request reaches a URL that does not map to an active Webhook node route, or the reverse proxy never forwards the request to n8n.
Key Facts
- Most common cause
- The caller is using a URL that does not match an active Webhook node route.
- Mode mismatch
- Test URLs and production URLs are different operating modes.
- Activation dependency
- Production webhook URLs require the workflow to be active.
- Self-hosted dependency
- Reverse proxy and WEBHOOK_URL settings affect generated webhook URLs.
Recommended Steps
- Confirm whether the external app is calling the test URL or the production URL.
- If using the production URL, confirm the workflow is active.
- Check the Webhook node path and HTTP method.
- For self-hosted n8n, confirm the public URL generated by n8n matches the real domain and proxy route.
- Send a small curl request to the exact URL and inspect the workflow executions list.
Verification
- The exact external URL appears in the Webhook node as the intended URL.
- A request from outside the server creates an execution.
- The response is no longer 404 for the configured method and path.
Warnings
- Do not fix a webhook 404 by switching to a test URL in a production integration.
- If a reverse proxy strips or rewrites paths, the request may never reach the Webhook node route.
Common Mistakes
- Copying the test URL into a third-party production setting.
- Forgetting to activate the workflow.
- Changing the Webhook node path after the external service already stored the old URL.
- Leaving WEBHOOK_URL pointed at localhost on a self-hosted instance.
Examples
URL copied from production tab: yes
Workflow active: yes
HTTP method matches node: yes
Webhook path unchanged: yes
Public domain reaches n8n: yes
Reverse proxy forwards /webhook/*: yesFAQ
Why does the browser show 404 but the editor test works?
The editor test may be using the test URL while the browser or external app is using the production URL. Confirm mode, activation, method, and path.
Can a reverse proxy cause webhook 404s?
Yes. If the proxy does not forward the webhook path to n8n, the request can return 404 before it reaches the workflow.