Makes sense that hostinger is the issue as there is no way Meta could allow such a error for so long. My client already wants n8n hosted on google cloud and I am moving it there and will let everyone know if I still have the missed messages issue.
This is John from Elestio here. Happy to help anyone looking at our platform. DM me if I pass on some promo credits for your testing
We moved the workflow from Hostinger to elest.io. Its working fine. The issue is with Hostinger
I had the same problems today but using the Facebook lead trigger. Thank you for your recommendations
1 Like
I tried Cloudflare and I think it worked
I did this and apparently it works.
1 Like
I’ve already resolved the issue. In short, yes—it has been confirmed that this is a Hostinger-related problem. Here’s a temporary, low-cost, and quick workaround you can use: Solución: Webhooks de Meta (WhatsApp) con Timeout o Retraso en Hostinger (Rate Limiting ASN 47583) - Azul School
3 Likes
que grande, muchas gracias!
Same issue here with VPS in Hostinger, the customer support team deny issues by their side. So it is suppose we have to live with this forever?
In my case, my n8n workflow not only recieve messages through the webhook but it sends messages as well to the WhatsApp API, what does happen then with the sent messages? are those delayed as well? or the issue is only at recieving?
They’ve already confirmed it, but they haven’t dared to release an official statement. In the link I left above in the comments, I posted a screenshot of the email where it’s confirmed. But it’s in Spanish.
The problem is only with incoming messages; there is no problem with outgoing messages.
1 Like
could you please confirm that the cloudfare approach worked fine?
Hi Everyone, I’m very new to this process and found the same issue when trying to connect whatsapp trigger node with n8n. A month ago I was able to do this normally, now I get this same error. Is this something that just happended recently? Hostinger told me there is no official confirmation on their side that this is a problem
1 Like
It’s a serious Hostinger issue and they’ve refused to address it, there is a someone who did a workaround with cloudfare, but I prefered to just switch to Elestio and I also didn’t use n8n cloud
It’s my first time being in the community and i didn’t know I can select a solution to solve the problem, so as not to confuse newcomers. Hostinger is not solving this issue any time soon.
There are 3 solutions to going about this;
-
An engineer by the name of @aseazul already showed fix with this via cloudfare.
-
Move to n8n cloud.
-
Move to Elestio.
2 Likes
I followed the tutorial but deploying the reverse proxy in render.com and the messages still have delay time to time… I will try with another VPS provider
1 Like
Then you should move to Elestio then, it has no errors, n8n cloud is expensive for us at the moment.
Ok I made to work it keeping my n8n server in Hostinger and using the approach of @aseazul in a render.com server, however, if you are using the “Whatsapp trigger“ node this is tricky, since everytime you save your workflow or you switch the “Active” toggle on or off, the “Whatsapp trigger“ will under the hood re-run the webhook subscrption again, (using the real domain and not the proxy one), overwriting it in the Meta webhook section.
You have here 2 options:
-
to use in this case the normal “Webhook” node, 2 of them, one of them with GET method to process webhook subscription and another one with POST method to read the webhook messages with the expected chatbot workflow.
-
Keep the “Whatsapp trigger” node but to re-introduce the proxy webhook url in the Meta panel section after updating your workflow every time.