Webhook Signature Validation Behind Reverse Proxy

If TLS termination happens upstream (e.g., Cloudflare or Traefik), can modified headers affect webhook signature validation for providers like Stripe?

Describe the problem/error/question

What is the error message (if any)?

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

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

Hi @Ogunmokun_Adeyemi , welcome to the n8n community :tada: !

I’d also check forwarded headers like content-encoding and transfer-encoding. If the proxy alters these without matching the body, it can cause subtle signature mismatches. Keeping headers and payload consistent is just as important as raw body integrity.