Last updated · May 2026
- Production-ready APIs
- SOC 2 Type I - In Progress
WEBHOOK_HOST_NOT_ALLOWED
HTTP 400 with next_step=contact_support. Your sink target is on the egress denylist.
What it means
DataVibe's egress guard refuses connections to private IP ranges (RFC1918, link-local, loopback, multicast, reserved) and to any host outside EGRESS_ALLOWED_DOMAINS when a strict allowlist is configured. This protects your data and ours from SSRF.
How to fix
- Confirm the destination is reachable on the public internet over HTTPS.
- If your operator team uses a strict allowlist, ask them to add the host suffix to
EGRESS_ALLOWED_DOMAINS. - Cloud-internal addresses (169.254.169.254, 10.x, 192.168.x, etc.) will never be allowed; route through a public ingress instead.