All External Webhooks Returning 404 on n8n Cloud (Internal Calls Work Normally)

Questions
1

Hi,

I’m encountering an issue on n8n Cloud where every external webhook request returns a 404, but webhooks triggered internally from another workflow work completely fine.

Environment

  • n8n Cloud instance: https://<my-instance>.n8n.cloud

  • Not self-hosted

  • Multiple workflows tested

  • Issue affects both production and test webhook URLs

Summary of the Problem

:cross_mark: External calls return 404

Any external request to:

https://<my-instance>.n8n.cloud/webhook/<id>
https://<my-instance>.n8n.cloud/webhook-test/<id>

responds with:

HTTP/2 404
server: cloudflare
content-type: application/json

This happens with:

  • Existing workflows

  • Newly created workflows

  • UUID paths

  • Simple paths (e.g., /webhook/slack-test)

:check_mark: Internal calls DO work

If Workflow A uses an HTTP Request node to call Workflow B’s webhook (same endpoint), the webhook executes correctly and the correct response is returned.

This confirms:

  • The webhook node exists

  • The workflow is active

  • The handler is functioning internally

  • The issue occurs before external requests reach n8n

Slack verification also fails

Slack sends the url_verification event but receives no valid response because n8n never sees the incoming request. Slack reports challenge_failed.

Troubleshooting Done

I’ve already tried:

  • Deactivating and reactivating workflows

  • Restarting the instance

  • Creating brand-new workflows

  • Using simple/non-UUID webhook paths

  • Testing from different networks

  • curl HEAD and POST requests

  • Sending both JSON payloads and empty requests

External webhook requests consistently return 404 from Cloudflare, indicating they aren’t reaching the n8n webhook handler at all.

Internal calls bypass the ingress layer and work correctly.

Likely Cause

It appears the ingress routing (Cloudflare → Traefik → n8n container) might not be forwarding external webhook traffic to my instance.
Since internal calls work, but external ones never reach n8n, this seems like an issue at the routing layer rather than a workflow configuration issue.

Request

Could someone from the n8n team please help reset or rebuild the webhook routing for my Cloud instance?
This is blocking Slack Event Subscriptions and any external integrations that depend on webhooks.

I’m happy to provide additional logs, curl output, workflow IDs, or anything else needed.

Thank you!

2

Hey anyone here to help?

I did another test, created a new workflow with nothing but webhook trigger, when I listen for test events I’m getting an error.

CleanShot 2025-12-12 at 09.26.27@2x
CleanShot 2025-12-12 at 09.26.27@2x1660×1054 58.2 KB

3

Hi @Jason_A

Sorry that you are having problems using n8n cloud and didn’t receive an answer. It looks like there might have been some bug on the n8n version you were using. I would suggest upgrading to the latest version and trying again. If that doesn’t please reach out and share your n8n cloud username, so I can take a look.

5

Yes, that’s what I’m thinking as well, you need to update your current n8n version to the latest.

Your instance has encountered a workspace-specific tenant-level routing issue (documented under GitHub issue #22782). The n8n Cloud ingress router (Cloudflare/Traefik) has lost synchronization with your workspace and is failing to register your production webhook paths.

Because this blockage happens at the cloud routing layer before external traffic ever reaches your specific container, toggling workflows, changing URLs, or restarting the instance from the UI will not force the router to resync.