This message was deleted.

This error indicates that Airbyte cannot resolve the hostname

hq1.appsflyer.com

(DNS/name resolution failure), so it never reaches the AppsFlyer API. From the knowledge sources, similar errors (

Name or service not known

,

name not resolved

) have been caused by: • Missing or incorrect DNS configuration on the host or Docker daemon. [Azure DNS issue; Chargebee name resolution; Zendesk name does not resolve] • Incorrect domain / subdomain values in the connector configuration (e.g., using a partial or malformed domain). [Freshsales domain fix] For AppsFlyer specifically, the source only requires: •

api_token

•

app_id

•

start_date

• optional

timezone

[AppsFlyer source] There is no custom domain field, so the problem is almost certainly networking/DNS, not the connector config itself. Recommended checks: 1. Verify DNS on the host and Docker: ◦ Ensure your host OS has valid nameservers configured (e.g., in

/etc/netplan/*.yml

on Ubuntu). [Azure DNS issue] ◦ If needed, set DNS in

/etc/docker/daemon.json

, e.g.:

{
  "dns": [
    "8.8.8.8",
    "1.1.1.1"
  ]
}

then restart Docker. 2. Test name resolution from inside the Airbyte worker container: ◦

docker exec -it airbyte-worker ping hq1.appsflyer.com

◦ If this fails, the issue is with container DNS/network, not AppsFlyer or Airbyte config. 3. Confirm there is no proxy/SSL middlebox rewriting the URL (the

'<http://hq1.appsflyer.com|hq1.appsflyer.com>'

pattern looks like something copied from a formatted message; Airbyte should be using plain

hq1.appsflyer.com

). If after fixing DNS the hostname still cannot be resolved from the container, the knowledge sources do not provide further AppsFlyer‑specific troubleshooting steps; at that point you’d need to investigate your infrastructure/network setup outside of Airbyte. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.