A 404 from a webhook usually means n8n cannot find a matching active endpoint.
Common causes
- Workflow inactive while using the production URL.
- Test URL used after the test listener ended.
- Wrong method: the sender uses POST but the node expects GET.
- Wrong path: a typo or an old path after you changed it.
- Wrong base URL: self-hosted n8n behind a proxy needs its public URL set correctly or it shows the wrong address.
- Proxy or firewall blocking the request.
How to debug
- Copy the URL exactly from the node.
- Call it from a simple request tool.
- Check the executions list for received calls.
- Look at proxy logs.
Remember
Local installs are not reachable from the internet: see installing n8n.
Related
Quick answers
What causes webhook 404?
Inactive workflow, wrong URL, path or method.
Why is the displayed URL wrong?
Your public URL setting may be missing behind a proxy.
Can I test from my computer?
Yes, with a simple request tool.
Related reading
- n8n Workflow Not Triggering: Common Causes and Fixes
- How to Handle Errors in n8n with an Error Workflow
- How to Debug n8n Executions and Data Problems
Want to learn n8n with a trainer, not just videos?
Our 15-day live n8n course takes you from the editor basics to APIs, messaging, AI agents and a final project, in Hindi and English. Fees start at ₹4,999 (final pricing may vary by format).
See the 15-day n8n training | Find your city | Book free counselling