Skip to content
deedglassdocs

destination_blocked

A connector’s destination is an address Deedglass never connects to: cloud metadata (even in dev), reserved or documentation ranges, an IPv6 address that embeds a blocked IPv4 one, loopback or a…

HTTP 400 · invalid_request_error · not retryable

What happened

Section titled “What happened”

A connector’s destination is an address Deedglass never connects to: cloud metadata (even in dev), reserved or documentation ranges, an IPv6 address that embeds a blocked IPv4 one, loopback or a private network outside dev, or Deedglass’s own database). Creating or updating the connector answers with this code and param: "config.base_url". A destination that changes its DNS answer later is caught when the call dials: the action is then failed with this error code and nothing was sent. Agents see a terse message that names no address; admins see the address and its class.

What to do

Section titled “What to do”

Point base_url at the service’s public address. To reach a private network in prod on purpose, list it in DEEDGLASS_EGRESS_ALLOW_CIDRS.

Example

Section titled “Example”
HTTP 400 · destination_blocked
{
  "error": {
    "type": "invalid_request_error",
    "code": "destination_blocked",
    "message": "base_url resolves to 169.254.169.254, a cloud metadata address. Deedglass never connects to it. Use the service's public address.",
    "param": "config.base_url",
    "request_id": "req_01j9zr3m5k8q2w7x4t6v0b1c9d",
    "doc_url": "https://docs.deedglass.com/errors/destination_blocked"
  }
}

The message is for a person and can get more exact over time: branch on type and code, never on the message.

In the SDKs

Section titled “In the SDKs”
SDK Raised as
TypeScript (@deedglass/sdk) InvalidRequestError with code === "destination_blocked"
Python (deedglass) deedglass.InvalidRequestError with .code == "destination_blocked"
Section titled “Related”