I’m hosting n8n on my Raspberry Pi5 with docker compose and use caddy to expose it to the internet with a duckdns domain.
Around two weeks ago, my WhatsApp and Slack Agent suddenly stopped working. I checked everything- literally- and nothing seems to be wrong. I checked all the logs, created new credentials, restarted, pulled the containers; I even changed a bit the Caddyfile, and nothing worked. So frustrating because I don’t know where this error could be and all the LLMs just talk trash.
Other Workflows without any API triggers work seamlessly-like the ones triggered by time. Webhook links also checked, responding 200-so all good there.
What I currently experience: When I run workflow in test mode, it gets in the mode of listening for any event. Then I write message and nothing happens, so it looks like n8n itself isn’t getting anything.
Pls help me, maybe you’ve had a similar experience.
Time triggers working rules out workers and DB issues. “When only inbound event-based triggers stop working, such as Slack or WhatsApp triggers, it’s almost always one of three things: public URL issues such as mismatches in WEBHOOK_URL, host or protocol, reverse proxy issues or Headers, or activations of the trigger’s behavior changing after an update.
Thanks for your response, I’ve already had these options configured within the same version before, thanks for your help, nonetheless.
For WhatsApp the App Settings for Renew has solved the problem.
With Slack the problem persists.
@elliston Sharing the incoming Slack payload (tokens removed) will greatly aid in identifying the specific area where the code fails and the actual fix for the code.
@elliston they send a url_verification event in order to verify your webhook url. It is important to ensure your endpoint responds back to Slack with just the JSON object {“challenge”: “…”} JSON in order for the webhook verification process to work successfully. It is important to ensure your active webhook is active and functioning properly.