Skip to content
Solución de problemas Admin

Webhooks aren't firing

Webhooks aren’t firing

Dailybot should call your HTTPS endpoint when events happen, but your receiver sees nothing. Outbound webhooks need a reachable URL, valid TLS, payloads under size limits, and a receiver that acknowledges quickly enough. Silent failures often mean retries exhausted after repeated errors.

Quick check

  • URL reachable — From an external host (not your laptop only), curl the URL with -v and confirm TCP + TLS complete.
  • Certificate chain — Use a publicly trusted cert; expired or incomplete chains cause hard fails.
  • HTTP status — Return 2xx fast; slow handlers cause timeouts.
  • Firewall — Allow Dailybot egress IPs if you enforce IP allowlists (confirm current list with support or docs).
  • Subscription toggles — Ensure the event types you expect are still enabled in Dailybot webhook settings.

Common causes and fixes

URL unreachable

DNS typos, internal-only hostnames, or shut-down tunnels (localhost on a developer machine) cannot work for production webhooks. Expose a public hostname or use a managed ingress. For testing, use a known webhook inspector temporarily, then replace with your service.

SSL certificate issue

Self-signed certs, wrong SANs, or legacy TLS versions break verification. Renew certificates before expiry. If you terminate TLS on a load balancer, upload the full chain. Test with SSL Labs or openssl s_client from outside your network.

Payload too large

Huge attachments or verbose diff payloads can exceed limits. Trim optional fields in the sender configuration if available, or increase receiver body limits and processing memory. If Dailybot offers compact modes, enable them.

Retry policy exhausted

After several non-2xx responses or timeouts, Dailybot may pause or disable the endpoint to protect the platform. Fix the receiver, then manually re-enable the webhook in settings and replay a test event if the UI provides one. Monitor your logs during replay.

Application logic rejecting valid posts

Signature verification bugs, wrong HMAC secret, or comparing JSON after pretty-print drift causes you to return 401 while thinking Dailybot never fired. Log the raw body before parsing. Temporarily disable verification in a secure test environment to confirm delivery, then restore verification with corrected code.

If none of this worked

Before contacting support, gather:

  • Webhook ID or name in Dailybot (non-secret)
  • Public hostname of your endpoint (no path secrets)
  • Time range (with timezone) when events should have fired
  • Whether your access logs show any hit from Dailybot user-agents or IPs
  • Recent changes to TLS, WAF, or auth
  • Steps you already tried from this article

Then contact Dailybot support from the Help or Contact options in the product or on the website.