WhatsApp Trigger: (#2200) Callback verification failed with the following errors: curl_errno = 56; curl_error = CONNECT tunnel failed, response 429; HTTP Status Code = 429; HTTP Message = Too Many Requests /
Hi, could someone help me solve this problem I’ve been having for a few days now? I’m desperate; I’ve tried everything and nothing has worked. I keep getting the same error in my WhatsApp trigger.
Hola @Datrueld , bienvenido a la comunidad!
Ese error 429 suele ser un bloqueo del proxy que uses (puede que Cloudflare?) porque se han superado los límites de peticiones.
Échale un ojo a la configuración del túnel o prueba a reiniciarlo para ver si con una IP nueva se soluciona.
También asegúrate de que el webhook en el panel de Meta coincida exactamente con lo que tienes en n8n, porque si hay errores en la verificación, Meta intenta conectar en bucle y acaba bloqueando la conexión.
¿Lo tienes en local o en algún servidor propio? Estas en hostinger puede ser?
Veo que se repite esta duda en el foro. Sospecho que es un problema generalizado.
@Datrueld Hello!
@DrPonka is right about the proxy/tunnel being the likely culprit. You’re not alone here — there are a bunch of threads from the last few days with the exact same CONNECT tunnel failed, response 429 error. It’s a widespread issue hitting self-hosted instances right now.
What’s actually happening is Meta tries to verify your callback URL when you activate the WhatsApp Trigger, but your hosting provider’s DDoS protection or proxy layer is intercepting that request and returning a 429 before it ever reaches n8n. That’s why the error says “CONNECT tunnel failed” even if you’re not using n8n’s built-in tunnel.
If you’re on Hostinger VPS — that’s almost certainly it. Multiple users have confirmed Hostinger’s edge firewall silently blocks Meta’s traffic. One user proved it by checking Traefik logs and seeing zero incoming requests from Meta even though WhatsApp showed blue ticks on the messages.
The workaround that’s working for people is putting Cloudflare in front of your domain with proxy mode (orange cloud) enabled. This masks your server IP behind Cloudflare’s trusted IPs, which bypasses the aggressive DDoS filtering.
Also if you’re still on the default SQLite database with a lot of active workflows, migrating to PostgreSQL can help with dropped webhooks under load. At least one user in the related threads confirmed the issue went away after switching to Postgres.
Quick way to confirm the root cause — copy the workflow to n8n Cloud (even a trial) and test. If it works there but not self-hosted, it’s your hosting infra, not your config.
Related threads with the same issue:
Hi, thank you so much for replying and trying to help, but my N8N is hosted on EasyPanel, and EasyPanel is hosted on Hostinger. I don’t know much about this; I’ve only been using N8N for a month and I don’t understand many things. I’ll try to fix this error with the advice you’ve given me. Thank you very much.
I have exactly the same problem. If you end up solving it, I’d be really pleased if you can share the solution with us.
I use EasyPanel hosted on Hosting as well
I’ll try looking around to see if there is any fixes!
@Julen @DrPonka on the hostinger status page, they seem to be doing maitnence right now.
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Scheduled - We are performing scheduled maintenance. Clients may experience service interruptions. We will provide further updates as necessary Server SG-479 maintenance
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 17, 2026 - 16:00 UTC
Scheduled - We are performing scheduled maintenance. Clients may experience service interruptions. We will provide further updates as necessary Server SG-479 maintenance
Are you suggesting these errors might be due to maintenance? Because I haven’t found a solution. I’m even considering switching to N8N Cloud.
Possibly, it’s the only thing I see going on at the moment @Datrueld
@Datrueld It could also just be hostinger since so many people right now are having hostinger problems because of what’sapp.
@echammAh I see. Yes, I’ve seen other people with this problem as well. It’s very frustrating. This error has stalled many of my projects, and I’ll continue looking for a solution if the problem isn’t related to maintenance. Thank you for your help.
Your welcome! I’ll let you know if I find any more info!
@echamm You’re the best, thank you
Your welcome!
anyways, I couldn’t find much on github or reddit, even on the n8n sections, it seems it’s only happening for n8n users.
One solution though is moving the traffic through cloudfare, so hostinger isnt blocking it.
1. Move your domain’s nameservers to Cloudflare (free plan works)
2. Add an A record pointing to your Hostinger VPS IP with the proxy toggle on (orange cloud icon)
3. Make sure n8n’s WEBHOOK_URL uses that domain (e.g. https://n8n.yourdomain.com) (or whatever your domain is)
4. Meta sends webhooks to n8n.yourdomain.com → hits Cloudflare first → Cloudflare forwards to your VPS
and then once hostinger is fixed, you can move it back, or you could just change hosting providers also.
This solution is also theoretical, no one has seemed to try it, a lot of people have just switched providers instead.
@achamm Thanks for the information, that’s what I’ll try. If it doesn’t work, I’ll have to switch providers. Do you have any recommendations? By the way, thanks again.
I like cloud n8n a lot, but if you have a old pc and you use tailscale which is free that works too.
hope this helps!
We are also facing the same issue. Please share the update, we hope it works. TIA
@achamm very well thank you =)
@Ravi_Teja_Guttula I haven’t been able to solve the problem yet, but if I do, I’ll let you know how. =)
We moved the workflow from Hostinger to elestio. Its working fine. The issue is with Hostinger