An egress destination is failing

Updated

When a destination can't deliver, you'll see egress/failed events and a lastError on the destination.

  1. Reachability — Synacl must reach your endpoint/host (open the firewall/allowlist).
  2. Credentials — re-check the token (InfluxDB), DB user/password (MariaDB), or SASL creds (Kafka).
  3. Target exists — bucket/table/topic must exist and be writable.
  4. Use Test — the Test button on the destination surfaces the exact error.
  5. Filter — if nothing arrives but there's no error, confirm the device+tag filter matches streams you actually produce.

Switched off by support? If Synacl support disabled the destination, the card says so with the reason and the time. Nothing is delivered until it is switched back on — you can re-enable it yourself with the toggle, which clears the notice.

Internal addresses are refused. A destination must point at a publicly reachable address. URLs resolving to loopback, private or link-local ranges are rejected when you save, and blocked at delivery time.

Per-type details: webhook · InfluxDB · MariaDB · Kafka.

More in Troubleshooting
My webhook action isn't firing
Checklist for debugging rule webhook deliveries.
My device shows offline
Step-by-step checklist when a device won't come online.
My messages are being throttled
Identify which limit you're hitting and how to fix it.
My gateway won't provision
When a gateway won't connect after flashing.
A firmware update failed
What to do when an OTA update doesn't complete.
My dashboard isn't updating
When widgets are blank or stale.